xCaliber healthCare Data Mesh

Interface Consent

Source Object: Interface Consent

Overview and Usage: The "Interface Consent" source object in athena EHR contains information related to patient consent for interfacing with third-party applications or vendors. This data is crucial for ensuring compliance with privacy and data sharing regulations, as well as for managing data exchange preferences. Key data fields include:

  • Consent By: Indicates the entity or individual granting consent (e.g., the patient).
  • Consent Date: Records the date when the consent was granted.
  • Consent Question: Specifies the question or request for which consent was obtained.
  • Consent Setting: Describes the context or setting in which the consent was given.
  • Consent Value: Represents the specific details or terms of the consent.
  • Interface Vendor ID: Identifies the vendor or third-party application involved.
  • Is Consenting: A binary field indicating whether consent has been given.
  • Patient ID: Contains the unique identifier of the patient.
  • Department ID: Identifies the department or healthcare facility where consent was obtained.

Developers can use the "Interface Consent" source object to create applications that manage patient consent preferences and data-sharing agreements. This is crucial for healthcare organizations to maintain transparency, comply with legal requirements, and facilitate secure data exchange with external systems. These applications can automate consent tracking, provide patients with control over their data sharing, and ensure compliance with privacy regulations, contributing to a seamless and secure healthcare ecosystem.

Mapping Table

Data FieldExample ValueSource Data Field DescriptionSource Field Data TypeSource Data Field CardinalityMapped FHIR++ ResourceMapped FHIR Data FieldAugmented MappingAssociated Coding SystemAssociated FHIR Data Field ExtensionMapping Context
consentby-The party deciding to give consent or not. This will either be PATIENT or PARENTGUARDIAN.String0..1Consentverification[1].verifiedWith-Top Level
consentdate-The date the consent decision was made.String0..1Consentverification[1].verificationDate-Top Level
consentquestion-The description text for the consent.String0..1Consentextension[*].valueString-consent-questionTop Level
consentsetting-The name of the setting for the interface vendor.String0..1Consentextension[*].valueString-consent-settingTop Level
consentvalue-The explicit value of the consent. This will be Y or N.String0..1Consentextension[*].valueString-consent-valueTop Level
interfacevendorid-The interface vendor ID.String0..1Consentorganization.reference-Top Level
isconsenting-This value will be 1 if the patient gives consent to the vendor. It is possible that the patient/gaurdian has not actively given consent, in which case this value is determined by whether the vendor is opt-in or opt-out.String0..1Consentverification[1].verified-Top Level
patientid-patient ID.String0..1Consentpatient.reference-Top Level
departmentid-Department ID.String0..1Consentextension[*].valueInteger-department-idTop Level