DocumentReference (63)

#NameSourceVerDescription
1ADHA Advance Care Planning Document DocumentReferenceau.digitalhealth.r4#currentR4The purpose of this profile is to provide a representation of an Advance Care Planning Document document reference for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia.
2ADHA Core DocumentReferenceau.digitalhealth.r4#currentR4The purpose of this profile is to provide a core representation of a document reference for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. This profile supports describing a document that is made available to a system and is used for documents that are not authored and assembled in FHIR e.g. documents whose form is an attachment.
3ADHA Diagnostic Report DocumentReferenceau.digitalhealth.r4#currentR4The purpose of this profile is to provide a representation of a Diagnostic Report document reference for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia. This profile is intended to be capable of supporting reporting for specialist and other diagnostic disciplines, pathology disciplines, and imaging disciplines.
4ADI Document Referencehl7.fhir.us.pacio-adi#currentR4This profile defines constraints that represent the information needed to register an advance directive information document on a FHIR server.
5APDDKDocumentReferencemedcom.fhir.dk.ihe.xds.metadata#currentR4A profile stating the rules, when exchanging a CDA Appointment (APD-DK) document.
6APDDKDocumentReferencemedcom.fhir.dk.metadata.apd#currentR4A profile stating the rules, when exchanging a CDA Appointment (APD-DK) document.
7Argonaut Clinical Notesfhir.argonaut.clinicalnotes#1.0.0R3
8Argonaut DocumentReference Profilefhir.argonaut.r2#1.0.0R2
9Arztbrieffhir.qpath4ms#currentR4Profile eines Arztbriefs
10AU Core DocumentReferencehl7.fhir.au.core#currentR4This profile sets minimum expectations for a DocumentReference resource to record, search, and fetch patient documents. It is based on the core FHIR [DocumentReference](http://hl7.org/fhir/R4/documentreference.html) resource and identifies the *additional* mandatory core elements, extensions, vocabularies and value sets that **SHALL** be present in the DocumentReference resource when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.
11AU Primary Care Attachmentau.csiro.fhir.au-primarycare#currentR4Document content as an attachment. This includes the binary content of the document as part of the entry. **Usage** Used to attach any relevant documents to the summary including their full content.
12Befundfhir.qpath4ms#currentR4Profile eines Befunds
13CH Core DocumentReferencech.fhir.ig.ch-core#currentR4Base definition for a document reference with the CH Core profiles.
14CH Core DocumentReference EPRch.fhir.ig.ch-core#currentR4Base definition for a document reference in the context of the electronic patient record (EPR).
15CH CRL DocumentReferencech.fhir.ig.ch-crl#0.9.0R4Definition of the DocumentReference for the report as PDF
16CH MHD DocumentReference Comprehensivech.fhir.ig.ch-epr-mhealth#currentR4CH MHD Profile on CH Core DocumentReference
17CH ORF DocumentReferencech.fhir.ig.ch-orf#currentR4Profile to describe how to provide a reference to a document to make it available to a healthcare system.
18CoreDocumentReferencemedcom.fhir.dk.metadata.core#currentR4A profile stating the rules, when exchanging a CDA document.
19CoreDocumentReferencemedcom.fhir.dk.ihe.xds.metadata#currentR4A profile stating the rules, when exchanging a CDA document.
20Document Reference Attachmenthl7.fhir.us.pq-cmc#currentR5A profile that represents the document or diagram in base64
21Document Reference to Patient's Personal Advance Care Plan (Advance Directive)hl7.fhir.us.mcc#currentR4This profile constrains US Core DocumentReference to reference, query for and retrieve Personal Advance Care Plans that exist for a patient.
22DocumentReferencehl7.fhir.nl.zorgviewer#currentR3Verwijzingen naar documenten
23DocumentReferencendhm.in#currentR4This profile sets minimum expectations for searching and fetching patient documents including the Clinical Notes using the DocumentReference resource.
24DocumentReference (Paronamix)hl7.eu.fhir.gk#currentR4This profile defines how the gaming results generated by the PANORAMIX project are shared within the Gatekeeper project by using the FHIR DocumentReference.
25DocumentReference - dx-PQhl7.fhir.uv.dx-pq#currentR5TBD
26DocumentReference - MDI Reporthl7.fhir.us.mdi#currentR4This DocumentReference profile constrains the US Core DocumentReference Profile to support exchanging death investigation documents, such as an Autopsy Report or Investigator’s Narrative. The content may be included as inline base64 encoded data or be provided by direct reference (e.g., URL). The document type is required and is constrained by US Core to a LOINC value whose SCALE is DOC in the LOINC database or is the HL7 v3 Code System NullFlavor concept 'unknown'.
27DocumentReference for Simplified Publishch.fhir.ig.ch-elm#currentR4A profile on the DocumentReference resource for Simplified Publish constraints. Simplified Publish - must be status current - must have an masterIdentifer - uses attachment.url to carry the document as a contained resource
28DocumentReference for Simplified Publish Responsech.fhir.ig.ch-elm#currentR4A profile on the DocumentReference resource for Simplified Publish Response constraints. Simplified Publish Response - must be status current - must have an identifer
29DocumentReference Inicio LEfhir.minsal.ListaDeEspera#currentR4DocumentReference Inicio LE
30DocumentReference Profile for metadata about the documenthl7.fhir.ca.baseline#currentR4Proposed constraints on the DocumentReference resource for the minimal set of data required to reference to a document of any kind for any purpose.
31DocumentReference resource for NZ Formularyhl7.org.nz.fhir.ig.formulary#currentR4BDocumentReference resource for NZ Formulary
32DocumentReference-IEHRfhir.uv.crossborderdataexchange#currentR4
33DocumentReference: PCSPhl7.eu.fhir.pcsp#currentR4This profile defines how to embed a PDF PCSP Survivor Passport in FHIR for the purpose of the PanCareSurPass project. This profile can be aslo used for send attachments (e.g Raditherapy reports or HDR) to the platform
34Dokumentfhir.qpath4ms#currentR4Profile eines Dokuments
35FutureAPDDKDocumentReferencemedcom.fhir.dk.ihe.xds.metadata#currentR4A profile stating the rules, when exchanging a CDA Appointment (APD-DK) document.
36Genomics DocumentReferencehl7.fhir.uv.genomics-reporting#currentR4A profile of DocumentReference used to represent a genomics file.
37IHE SDC/eCP on FHIR DocumentReferencehl7.fhir.uv.ihe-sdc-ecc#currentR4A DocumentReference Profile meant to share an IHE SDC Form whether completed or blank
38IPA-DocumentReferencehl7.fhir.uv.ipa#currentR4Minimum expectations for a DocumentReference resource when accessed via a International Patient Access API
39Just a simple profile of DocumentReferencejohnmoehrke.testbinary#currentR5not much to say
40Konsiliarberichtfhir.qpath4ms#currentR4Profile eines Konsiliarberichts
41Laborergebnisfhir.qpath4ms#currentR4Profile eines Laborergebnisses
42Lesser than MHD Minimal Document Referencejohnmoehrke.testmultirelease.example#currentR4BTake away identifier
43ManaakiNgaTahiDocumentReferencecinc.fhir.ig#currentR4DocumentReference FHIR resource for Manaaki Nga Tahi
44MedNet Interface (MNI) - DocumentReferenceswiss.mednet.fhir#0.15.0R4MedNet Interface (MNI) - DocumentReference Profile
45MHD DocumentReference Comprehensiveihe.iti.mhd#currentR4A profile on the DocumentReference resource for MHD Comprehensive Option with Contained (not UnContained), compatible with XDS-on-FHIR and XCA use. - MHD is based on the [IHE Document Sharing](https://profiles.ihe.net/ITI/HIE-Whitepaper/index.html) model, - the [3:4.1 Abstract Metadata Model](https://profiles.ihe.net/ITI/TF/Volume3/ch-4.1.html#4.1), and - the use defined here is FHIR DocumentReference implementation of the - ebRIM implementation at [3:4.2.3.2 Document Entry](https://profiles.ihe.net/ITI/TF/Volume3/ch-4.2.html#4.2.3.2). - with use-cases and constraints found in [3:4.3 Additional Document Sharing Requirements](https://profiles.ihe.net/ITI/TF/Volume3/ch-4.3.html#4.3)
46MHD DocumentReference Comprehensive UnContained References Optionihe.iti.mhd#currentR4A profile on the DocumentReference resource for MHD with Comprehensive Metadata Option but without a requirement for contained author, authenticator, or sourcePatientInfo. - MHD is based on the [IHE Document Sharing](https://profiles.ihe.net/ITI/HIE-Whitepaper/index.html) model, - the [3:4.1 Abstract Metadata Model](https://profiles.ihe.net/ITI/TF/Volume3/ch-4.1.html#4.1), and - the use defined here is FHIR DocumentReference implementation of the - ebRIM implementation at [3:4.2.3.2 Document Entry](https://profiles.ihe.net/ITI/TF/Volume3/ch-4.2.html#4.2.3.2). - with use-cases and constraints found in [3:4.3 Additional Document Sharing Requirements](https://profiles.ihe.net/ITI/TF/Volume3/ch-4.3.html#4.3)
47MHD DocumentReference for Simplified Publishihe.iti.mhd#currentR4A profile on the DocumentReference resource for MHD Simplified Publish constraints. - MHD is based on the [IHE Document Sharing](https://profiles.ihe.net/ITI/HIE-Whitepaper/index.html) model, - the [3:4.1 Abstract Metadata Model](https://profiles.ihe.net/ITI/TF/Volume3/ch-4.1.html#4.1), and - the use defined here is FHIR DocumentReference implementation of the - ebRIM implementation at [3:4.2.3.2 Document Entry](https://profiles.ihe.net/ITI/TF/Volume3/ch-4.2.html#4.2.3.2). - with use-cases and constraints found in [3:4.3 Additional Document Sharing Requirements](https://profiles.ihe.net/ITI/TF/Volume3/ch-4.3.html#4.3) Simplified Publish - Similar to Minimal Metadata constraints - must be status current - must have a patient indicated - uses attachment.data to carry the document, rather than attachment.url - so that the Simplified Publish is a simple POST of the DocumentReference - Document Recipient is expected to extract the .data, use .url
48MHD DocumentReference Minimalihe.iti.mhd#currentR4A profile on the DocumentReference resource for MHD with minimal metadata constraints. - MHD is based on the [IHE Document Sharing](https://profiles.ihe.net/ITI/HIE-Whitepaper/index.html) model, - the [3:4.1 Abstract Metadata Model](https://profiles.ihe.net/ITI/TF/Volume3/ch-4.1.html#4.1), and - the use defined here is FHIR DocumentReference implementation of the - ebRIM implementation at [3:4.2.3.2 Document Entry](https://profiles.ihe.net/ITI/TF/Volume3/ch-4.2.html#4.2.3.2). - with use-cases and constraints found in [3:4.3 Additional Document Sharing Requirements](https://profiles.ihe.net/ITI/TF/Volume3/ch-4.3.html#4.3)
49MIPHRDocumentReferencehl7.fhir.mi.phr#currentR4
50Nictiz IHE MHD Profile on DocumentReference (DocumentEntry) when used in the Provide Transaction with Minimal Metadata, see Table 3:4.3.1-3.nictiz.fhir.nl.stu3.zib2017#2.2.15R3Copied profile on DocumentReference based on IHE IT Infrastructure Technical Framework Supplement - Mobile access to Health Documents (MHD) Rev. 2.3. See http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD). The IHE MHD Profile text is Normative, this conformance resource is Informative.
51no-basis-DocumentReferencehl7.fhir.no.basis#2.1.2R4Basisprofil for Norwegian DocumentReference. Defined by The Norwegian Directorate of eHealth and HL7 Norway. The profile adds terminology and extensions specific to Norway. The basis profile is open, derived profiles should close down the information elements according to specification relevant to the use-case. The profile sets the absolute minimum requirements when searching, fething and storing documents within the healtcare domain. It sets the basic requirements for extensions and terminology which can be present.
52NPFS DocumentReferenceihe.iti.npfs#currentR4A profile on the DocumentReference resource for NPFS.
53PACIO ADI Document Referencehl7.fhir.us.pacio-adi#currentR4This profile defines constraints that represent the information needed to register an advance directive information document on a FHIR server.
54PDSm Comprehensive DocumentReferenceans.fhir.fr.pdsm#3.0.1R4Profil spécifique dérivé du profil IHE MHD v4.0.1 "ComprehensiveDocumentReference" créé pour le volet "Partage de documents de santé en mobilité".
55PDSm Simplified Publishans.fhir.fr.pdsm#3.0.1R4Ce profil a été créé en s'inspirant du profil MHD Simplified. Contrairement au profil PDSm_ComprehensiveDocumentReference, le document est directement inclus dans DocumentReference.attachment.data et non dans une ressource « Binary » externe. Ce profil est utilisé dans le cadre du flux 9. Le flux et le profil sont inspirés d’IHE MHD, version build au 03.10.22 : transaction ITI-105 et du profil SimplifiedPublish.DocumentReference. La publication simplifiée est un simple POST d'une ressource DocumentReference conforme à ce profil.
56QRDDKDocumentReferencemedcom.fhir.dk.ihe.xds.metadata#currentR4A profile stating the rules, when exchanging a CDA Questionnaire Response Document (QRD-DK).
57QRDDKDocumentReferencemedcom.fhir.dk.metadata.qrd#currentR4A profile stating the rules, when exchanging a CDA Questionnaire Response Document (QRD-DK).
58Referencia de Documentoshl7.fhir.co.CoreCO#currentR4Docuento utilizado para guardar referencias.
59Rezeptfhir.qpath4ms#currentR4Profile eines Rezepts
60RR DocumentReferencehl7.fhir.us.ecr#currentR4This profile represents external resources such as a text guidance, link to access forms for additional reporting needs, additional testing and/or laboratory testing needs, treatment and/or prevention resources, Public Health Agency contact information and general additional resources.
61Sonstiges Dokumentfhir.qpath4ms#currentR4Profile eines sonstiges Dokuments
62SPLDocumentReferencehl7.fhir.us.spl#currentR4BA profile that represents the SPL document that was either created by or was the source for the Organization FHIR Bundle.
63US Core DocumentReference Profilehl7.fhir.us.core#currentR4To promote interoperability and adoption through common implementation, this profile sets minimum expectations for searching and fetching patient documents including Clinical Notes using the DocumentReference resource. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present and constrains the way the elements are used when using the profile. It provides the floor for standards development for specific use cases. Prior to reviewing this profile, implementers are encouraged to read the Clinical Notes Guidance to understand the overlap of US Core DocumentReference Profile and US Core DiagnosticReport Profile for Report and Note exchange.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
DocumentReference I C I I D D
DocumentReference.id D
DocumentReference.indexed C C
DocumentReference.created C C C
DocumentReference.class C B M
DocumentReference.authenticator C D C I I
DocumentReference.masterIdentifier C D C D C C C C D C
DocumentReference.masterIdentifier.value F F C C F F F
DocumentReference.masterIdentifier.system F F C C F F F
DocumentReference.meta
DocumentReference.meta.versionId I I
DocumentReference.meta.profile C
DocumentReference.meta.lastUpdated
DocumentReference.implicitRules C
DocumentReference.language
DocumentReference.text
DocumentReference.contained C
DocumentReference.extension S C (3) S C (2) S C (2) S (2) S C (2) S C (2) S C (2) S C (2) S C (3)
DocumentReference.modifierExtension C C C C
DocumentReference.identifier C C C C C C D S C C S C (2) C D S C
DocumentReference.identifier.value C
DocumentReference.identifier.system C
DocumentReference.version
DocumentReference.basedOn
DocumentReference.status F F C B M C B M F F D F F F F F F F F F B M F D F D F F F B M
DocumentReference.docStatus F F F C F C D C C D F F C C C D F F
DocumentReference.modality
DocumentReference.type B M C B M B M B M C B M C B M F C C F B M C B M C B M C C C B M C D B M C B M B M B M F F C C D B M C C B M I B M I D B M C F C C B M
DocumentReference.type.coding C C S C (2) C
DocumentReference.type.coding.display
DocumentReference.type.coding.code C C C F C C C F
DocumentReference.type.coding.system C C F C F C F B M B M F
DocumentReference.type.text C
DocumentReference.category S C F (2) C B M B M F C F B M C B M C B M C B M C B M C F D B M C F F C C C C B M C B M I B M I B M F C B M F S C B M (2)
DocumentReference.category.coding S C (3)
DocumentReference.category.coding.display
DocumentReference.category.coding.code C C C F (2)
DocumentReference.category.coding.system C C C F (2)
DocumentReference.subject C I C C C C C C C D C D C C C C C D C C I C C C
DocumentReference.subject.reference C C C C
DocumentReference.context C C C C C C
DocumentReference.context.related D C
DocumentReference.context.related.ref D
DocumentReference.context.related.identifier D
DocumentReference.context.sourcePatientInfo C D C D C
DocumentReference.context.sourcePatientInfo.identifier
DocumentReference.context.sourcePatientInfo.reference
DocumentReference.context.period C C I C
DocumentReference.context.period.end
DocumentReference.context.period.start C
DocumentReference.context.practiceSetting B M B M B M B M C B M C C D B M B M C I B M I B M
DocumentReference.context.practiceSetting.coding
DocumentReference.context.practiceSetting.coding.code C C
DocumentReference.context.practiceSetting.coding.system C C B M B M
DocumentReference.context.facilityType B M B M B M B M C B M C C B M C I B M I B M
DocumentReference.context.facilityType.coding
DocumentReference.context.facilityType.coding.code C C
DocumentReference.context.facilityType.coding.system C C B M B M
DocumentReference.context.event B M B M C C B M C I C I
DocumentReference.context.event.coding
DocumentReference.context.event.coding.code C C
DocumentReference.context.event.coding.system C C B M B M
DocumentReference.context.encounter C C D C C
DocumentReference.context.encounter.reference C
DocumentReference.event
DocumentReference.bodySite
DocumentReference.facilityType
DocumentReference.practiceSetting
DocumentReference.period
DocumentReference.date C C C C C C C D C C C D C
DocumentReference.author C C I C C C C D D D D C C I C I C
DocumentReference.author.reference C C C
DocumentReference.attester
DocumentReference.attester.extension
DocumentReference.attester.modifierExtension
DocumentReference.attester.mode
DocumentReference.attester.time
DocumentReference.attester.party
DocumentReference.custodian C C C C D C
DocumentReference.custodian.reference C
DocumentReference.relatesTo D I D I D
DocumentReference.relatesTo.extension
DocumentReference.relatesTo.modifierExtension
DocumentReference.relatesTo.code
DocumentReference.relatesTo.target I
DocumentReference.description F F C D F F F C D F
DocumentReference.securityLabel F F B M C C D B M B M F F C C D I I F F
DocumentReference.content C C C C C C D C D C C C D C D C
DocumentReference.content.format C B M C B M B M C B M C B M C B M C B M D C B M B M C I B M I B M B M
DocumentReference.content.extension
DocumentReference.content.modifierExtension
DocumentReference.content.attachment C I C I I D I I
DocumentReference.content.attachment.creation C C D C C D
DocumentReference.content.attachment.hash D C C
DocumentReference.content.attachment.size D C C
DocumentReference.content.attachment.title C C D C C C
DocumentReference.content.attachment.language B M C B M C B M C B M C B M C C
DocumentReference.content.attachment.url C C D C C C C C C C C C I C C
DocumentReference.content.attachment.data C C C C D C C C C C C C C D C C C
DocumentReference.content.attachment.contentType C C C I C I C C B M C B M C B M C C C F C C C C C C C C
DocumentReference.content.profile
DocumentReference.content.profile.extension
DocumentReference.content.profile.modifierExtension
DocumentReference.content.profile.value[x]
S: There is slicing defined in the element(s)
C: There is cardinality erstrictions defined in the element(s)
I: There is invariants defined in the element(s)
F: There is a fixed or pattern value defined in the element(s)
D: There is document provided in the element(s)
B: There is terminology bindings defined in the element(s)
M: At least one of the element(s) has must-support = true
(N): The number of elements if > 1

Produced 08 Sep 2023