Determining the consent management process for patients
Summarize
Summary of Determining the Consent Management Process for Patients
This guide provides instructions on how to configure the consent management process for patients within a healthcare organization using the snhcls.admin role. It outlines the types of consent policies available and how they can be implemented to ensure compliance with privacy regulations.
Show less
Key Features
- Standard Document Policy: This policy type does not require a patient’s consent form to be reviewed or signed. Patients must sign the consent for each service requested.
- Document Policy: This policy requires a consent form to be reviewed and signed by the patient. A to-do item is generated for the patient to sign the consent form, which must be configured along with decision rules.
- Validity Duration: The privacy policy allows you to specify how long the consent remains valid after a patient signs it. During this period, consent is valid for multiple healthcare requests.
- Automatic Inactivation: A scheduled job automatically sets any policy consent to inactive once its validity duration expires.
- Document Attachment: After consent is given, the consent document is attached to the policy consent record, linking it to the initial healthcare request.
Key Outcomes
By implementing the consent management process, healthcare organizations can streamline patient consent collection, ensuring compliance and improving the patient experience. A patient only needs to give consent once for all requests within the validity period. If the consent is still active and the request is within the validity duration, the existing consent can be used; otherwise, a new consent request will be initiated.
You can determine whether the privacy policy for patient consent needs to be routed for review and signature to the patient.
As a user with the sn_hcls.admin role, you can configure a privacy policy for obtaining consent from patients in a healthcare organization. For more information, see Configure a privacy policy for managing patient consent.
You can determine the consent management process as one of the following types:
Configuring standard policy types
A standard policy doesn't require a consent form to be reviewed or signed by a patient.
With the Standard policy type, a patient is required to sign the same consent again and again each time a service is requested.
Configuring document policy types
A document policy requires a consent form to be reviewed, signed, or both by a patient.
With the Document template policy type, a to-do item is created for the patient to sign the consent form.
When setting up the privacy policy, you can also specify the validity duration in days for the consent after a patient signs the consent form. An accepted consent for an active policy is valid for multiple healthcare requests until the validity duration specified in the policy starting from date when the consent was given. Therefore, a patient needs to give consent only once for all healthcare requests submitted during the validity duration of an active consent policy. By default, the Set inactive status for expired policy consents scheduled job is configured to set any policy consent as inactive when the policy validity duration has expired.
After a patient gives the consent, the consent document is added as an attachment to the policy consent. The case associated with the initial healthcare request for which the consent was given is associated with the policy consent record.
- The consent privacy policy is still active.
- The case was created within the validity duration of the accepted consent.
- The document decision rule of the document template associated with the new case is met.
When working on a healthcare case, a healthcare agent can then review and verify the accepted consent. If no consent was accepted, the healthcare agent has to wait until the patient gives the consent.