ChronicCareIQ has updated the patient consent panel and is moving toward supporting multiple consent options and dates for different billing types. This update will allow the ability to specifically consent patients to a certain billing type and allows for edits over the course of the patient’s active enrollment in ChronicCareIQ.
NOTE: Technology connected patients will still give their consent via the ChronicCareIQ portal activation process. This process will NOT change for new patients. Established technology patients who have a new billing type added WILL be asked to reconsent to their monitoring programs on the first login after their billing type is updated.
The staff view of the new consent UI panel will be seen by all clients starting January 2025. The UI will only show the billing types that each client supports, not all types. Here is an example for a client that supports all billing types that ChronicCareIQ currently offers:
The first area to notice is that the general consent status of the patient has relocated to the top left hand corner under “Generate Billing Codes for Patient”. This placement brings the overall status of the patient to its own location:
Next, each billing type can now be consented separately as needed. This update allows clients to have more control over billing types and consent for each patient. It also allows for clients who begin their ChronicCareIQ program as one billing type, such as CCM, but then expand into other programs (such as RPM, BHI, etc.) to be separately noted.
For example, in this patient, the CCM consent has been given but the patient has not yet consented to their RPM program. This can be separately documented within ChronicCareIQ:
The consent will also be captured on the patient chart and dashboard with the consent types clearly struck through if the patient has not been marked as consented in ChronicCareIQ:
This new consent panel sets the stage for documenting multiple consents within ChronicCareIQ, especially for our partners who expand into adding APCM billing to current patients, which requires a specific consent outlined by CMS. As our consent functionality expands, we will be sure to include those updates in future release notes for client review.