Determining the consent management process for patients
Summarize
Summary of Determining the Consent Management Process for Patients
This guide outlines the process for managing patient consent within healthcare organizations using the ServiceNow platform, specifically for users with thesnhcls.adminrole. It focuses on configuring privacy policies for obtaining patient consent and the types of consent management processes available.
Show less
Key Features
- Standard Document: Does not require a signed consent form. Patients must sign consent repeatedly for each service requested.
- Document Policy: Requires a consent form to be reviewed and/or signed. A to-do item is created for patients to sign the consent form, which must be configured alongside decision rules.
- Validity Duration: You can specify the number of days the consent remains valid after signing. Patients only need to provide consent once for all requests during the validity period.
- Inactive Status for Expired Consents: A scheduled job automatically sets expired consent policies to inactive.
- Case Association: The consent document is attached to the policy consent record and associated with the initial healthcare request. New cases can be linked to existing consents if criteria are met; otherwise, a new consent request is generated.
Key Outcomes
By effectively managing patient consent through this process, healthcare agents can streamline consent verification for multiple requests within the validity period, ensuring compliance and enhancing patient experience. If consent is not accepted, agents must wait for the patient to provide it before proceeding with care. This system simplifies tracking and managing consent across healthcare interactions.
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.