Table 3 Summary of evaluated common standards, profiles, and formats
From: MAGIC: once upon a time in consent management—a FHIR® tale
Name | Description |
|---|---|
HL7 FHIR (standard) | Health Level Seven International (HL7) Fast Healthcare Interoperable Resources (FHIR), a REST-based standard for interoperability in healthcare to access distributed information (e.g. patient, medication and treatment) in a uniform, open format using JSON and XML [30] |
HL7 v2 (standard) | A standard for information transfer and to support system integration processes, e.g. to exchange patient-, performance- or finding-related information within hospitals [45] |
HL7 CDA (standard) | Clinical Document Architecture (CDA) is a standard for document-based information exchange in primarily clinical use cases. CDA offers the possibility to combine human-readable and machine-readable contents [46] |
IHE BPPC (profile) | The IHE profile Basic Patient Privacy Consents (BPPC) allows basic and non-recurring documentation of a patient’s consent regarding the exchange of his/her data between cooperating facilities (e.g. hospitals). [27] |
IHE APPC (profile) | The IHE profile Advanced Patient Privacy Consents (APPC) is a profile [28] describing how to use a domain specific language for access control rules to create a policy document. It focusses on how to reference data communicated using other IHE profiles (e.g. IHE XDS) in that language. It also contains rules for how to transmit such a policy document using IHE document sharing profiles. While the underlying standards for these highly structured policy documents enable automatic enforcement, the profile itself does not contain any of those transactions, only the policy document structure, and metadata [47] |
XML (format) | Extensible Markup Language (XML), a format for the structured description of data [29] |
JSON (format) | JavaScript Object Notation (JSON), a simple format for data. No additional functionality [29] |