Determining the consent management process for patients
Summarize
Summary of Determining the Consent Management Process for Patients
This document outlines how to configure the consent management process for patients within a healthcare organization using the ServiceNow platform. Users with thesnhcls.adminrole can establish privacy policies for obtaining patient consent and determine the routing requirements for review and signature.
Show less
Key Features
- Policy Types: Users can configure two types of consent policies:
- Standard Document: Requires patients to sign consent for each service request.
- Document Policy: Requires patients to review and sign a consent form, creating a to-do item for them.
- Validity Duration: Administrators can specify how long the consent remains valid after being signed, allowing patients to provide consent once for multiple requests during that period.
- Policy Management: Only one active policy can be associated with a document template, and expired policies are automatically set to inactive.
Key Outcomes
Upon configuration, the consent document is attached to the policy consent record. Subsequent healthcare requests can utilize the accepted consent as long as the policy remains active, the request is within the validity duration, and the document decision rules are met. If conditions are not met, a new consent request will be generated for the patient.
Healthcare agents can review and verify accepted consents, ensuring compliance and streamlining the patient experience. If no consent exists, agents must wait for the patient to provide it before proceeding.
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.