Patient Consent Management > Patient Consent Management contents > Patient Consent Management recipe assets
  

Patient Consent Management recipe assets

The Patient Consent Management recipe contains FHIR, Docusign, and email app connections; Docusign and FHIR service connectors; and processes to intiate the patient consent workflow and post the consent to FHIR.
The following table describes the assets that the Patient Consent Management recipe package contains:
Asset Name
Asset Type
Description
AppConnectionforFHIR
App connection
App connection for the FHIR server.
DocusignConnection
App connection
App connection that calls the Docusign REST API.
Docusign Connector
Service connector
Connector that exposes various actions of Docusign.
EmailAppConnection
App connection
Email connection to send an email.
FHIR_Connector
Service connector
Bidirectional service connector that can be used to retrieve or send data to the FHIR server.
Initiate Patient Consent Workflow
Process
Process to initiate the Patient Consent Management process.
Patient Consent Management
Process
Process to post the consent to the FHIR server and send the consent document to the Docusign for patient's signature. It waits until the document is signed and updates FHIR based on the document status.
Post Consent to FHIR Server
Process
Process to send Consent resource to the FHIR server.
Send Patient Consent for eSignature
Process
Process to send the consent document template to Docusign for eSignature.