Beschreibung
Dieses Profil beschreibt ein Dokument / Publikation in der Medizininformatik-Initiative.
Name | Canonical |
---|---|
MII_PR_Studie_Dokument | https://www.medizininformatik-initiative.de/fhir/modul-studie/StructureDefinition/mii-pr-studie-dokument |
Differential
DocumentReference | I | DocumentReference | There are no (further) constraints on this element Element IdDocumentReference A reference to a document DefinitionA reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text. Usually, this is used for documents other than those defined by FHIR.
| |
masterIdentifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdDocumentReference.masterIdentifier Master Version Specific Identifier DefinitionDocument identifier as assigned by the source of the document. This identifier is specific to this version of the document. This unique identifier may be used elsewhere to identify this version of the document. The structure and format of this Id shall be consistent with the specification corresponding to the formatCode attribute. (e.g. for a DICOM standard document a 64-character numeric UID, for an HL7 CDA format a serialization of the CDA Document Id extension and root in the form "oid^extension", where OID is a 64 digits max, and the Id is a 16 UTF-8 char max. If the OID is coded without the extension then the '^' character shall not be included.). CDA Document Id extension and root.
|
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element IdDocumentReference.identifier Other identifiers for the document DefinitionOther identifiers associated with the document, including version independent identifiers.
|
status | S Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element IdDocumentReference.status current | superseded | entered-in-error DefinitionThe status of this document reference. This is the status of the DocumentReference object, which might be independent from the docStatus element. This element is labeled as a modifier because the status contains the codes that mark the document or reference as not currently valid. The status of the document reference. DocumentReferenceStatus (required)Constraints
|
docStatus | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdDocumentReference.docStatus preliminary | final | amended | entered-in-error DefinitionThe status of the underlying document. The document that is pointed to might be in various lifecycle states. Status of the underlying document. CompositionStatus (required)Constraints
|
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdDocumentReference.type Kind of document (LOINC if possible) DefinitionSpecifies the particular kind of document referenced (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the document referenced. Key metadata element describing the document that describes he exact type of document. Helps humans to assess whether the document is of interest when viewing a list of documents. Precise type of clinical document. DocumentTypeValueSet (preferred)Constraints
|
category | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdDocumentReference.category Categorization of document Alternate namesclaxs DefinitionA categorization for the type of document referenced - helps for indexing and searching. This may be implied by or derived from the code specified in the DocumentReference.type. Key metadata element describing the the category or classification of the document. This is a broader perspective that groups similar documents based on how they would be used. This is a primary key used in searching. High-level kind of a clinical document at a macro level. DocumentClassValueSet (example)Constraints
|
subject | Σ I | 0..1 | Reference(Patient | Practitioner | Group | Device) | There are no (further) constraints on this element Element IdDocumentReference.subject Who/what is the subject of the document DefinitionWho or what the document is about. The document can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of farm animals, or a set of patients that share a common exposure). References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Patient | Practitioner | Group | Device) Constraints
|
date | Σ | 0..1 | instant | There are no (further) constraints on this element Element IdDocumentReference.date When this document reference was created Alternate namesindexed DefinitionWhen the document reference was created. Referencing/indexing time is used for tracking, organizing versions and searching.
|
author | S Σ I | 0..* | Reference(Practitioner | PractitionerRole | Organization | Device | Patient | RelatedPerson) | There are no (further) constraints on this element Element IdDocumentReference.author Who and/or what authored the document DefinitionIdentifies who is responsible for adding the information to the document. Not necessarily who did the actual data entry (i.e. typist) or who was the source (informant). Reference(Practitioner | PractitionerRole | Organization | Device | Patient | RelatedPerson) Constraints
|
authenticator | I | 0..1 | Reference(Practitioner | PractitionerRole | Organization) | There are no (further) constraints on this element Element IdDocumentReference.authenticator Who/what authenticated the document DefinitionWhich person or organization authenticates that this document is valid. Represents a participant within the author institution who has legally authenticated or attested the document. Legal authentication implies that a document has been signed manually or electronically by the legal Authenticator. Reference(Practitioner | PractitionerRole | Organization) Constraints
|
custodian | S I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element IdDocumentReference.custodian Organization which maintains the document DefinitionIdentifies the organization or group who is responsible for ongoing maintenance of and access to the document. Identifies the logical organization (software system, vendor, or department) to go to find the current version, where to report issues, etc. This is different from the physical location (URL, disk drive, or server) of the document, which is the technical location of the document, which host may be delegated to the management of some other organization.
|
relatesTo | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element IdDocumentReference.relatesTo Relationships to other documents DefinitionRelationships that this document has with other document references that already exist. This element is labeled as a modifier because documents that append to other documents are incomplete on their own.
|
code | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element IdDocumentReference.relatesTo.code replaces | transforms | signs | appends DefinitionThe type of relationship that this document has with anther document. If this document appends another document, then the document cannot be fully understood without also accessing the referenced document. The type of relationship between documents. DocumentRelationshipType (required)Constraints
|
target | Σ I | 1..1 | Reference(DocumentReference) | There are no (further) constraints on this element Element IdDocumentReference.relatesTo.target Target of the relationship DefinitionThe target document of this relationship. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
description | Σ | 0..1 | string | There are no (further) constraints on this element Element IdDocumentReference.description Human-readable description DefinitionHuman-readable description of the source document. Helps humans to assess whether the document is of interest. What the document is about, a terse summary of the document.
|
securityLabel | Σ | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element IdDocumentReference.securityLabel Document security-tags DefinitionA set of Security-Tag codes specifying the level of privacy/security of the Document. Note that DocumentReference.meta.security contains the security labels of the "reference" to the document, while DocumentReference.securityLabel contains a snapshot of the security labels on the document the reference refers to. Use of the Health Care Privacy/Security Classification (HCS) system of security-tag use is recommended. The confidentiality codes can carry multiple vocabulary items. HL7 has developed an understanding of security and privacy tags that might be desirable in a Document Sharing environment, called HL7 Healthcare Privacy and Security Classification System (HCS). The following specification is recommended but not mandated, as the vocabulary bindings are an administrative domain responsibility. The use of this method is up to the policy domain such as the XDS Affinity Domain or other Trust Domain where all parties including sender and recipients are trusted to appropriately tag and enforce. In the HL7 Healthcare Privacy and Security Classification (HCS) there are code systems specific to Confidentiality, Sensitivity, Integrity, and Handling Caveats. Some values would come from a local vocabulary as they are related to workflow roles and special projects. Security Labels from the Healthcare Privacy and Security Classification System. All Security Labels (extensible)Constraints
|
content | S Σ | 1..* | BackboneElement | There are no (further) constraints on this element Element IdDocumentReference.content Document referenced DefinitionThe document and format referenced. There may be multiple content element repetitions, each with a different format.
|
attachment | S Σ I | 1..1 | Attachment | There are no (further) constraints on this element Element IdDocumentReference.content.attachment Where to access the document DefinitionThe document or URL of the document along with critical metadata to prove content has integrity. When providing a summary view (for example with Observation.value[x]) Attachment should be represented with a brief display text such as "Signed Procedure Consent".
|
contentType | S Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.contentType Mime type of the content, with charset etc. DefinitionIdentifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate. Processors of the data need to be able to know how to interpret the data. Note that FHIR strings SHALL NOT exceed 1MB in size The mime type of an attachment. Any valid mime type is allowed. Mime Types (required)Constraints
General text/plain; charset=UTF-8, image/png Mappings
|
language | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.language Human language of the content (BCP-47) DefinitionThe human language of the content. The value can be any valid value according to BCP 47. Users need to be able to choose between the languages in a set of attachments. Note that FHIR strings SHALL NOT exceed 1MB in size A human language. CommonLanguages (preferred)Constraints
General en-AU Mappings
|
data | 0..1 | base64Binary | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.data Data inline, base64ed DefinitionThe actual data of the attachment - a sequence of bytes, base64 encoded. The data needs to able to be transmitted inline. The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON.
| |
url | S Σ | 1..1 | url | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.url Uri where the data can be found DefinitionA location where the data can be accessed. The data needs to be transmitted by reference. If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.
General http://www.acme.com/logo-small.png Mappings
|
size | S Σ | 0..1 | unsignedInt | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.size Number of bytes of content (if url provided) DefinitionThe number of bytes of data that make up this attachment (before base64 encoding, if that is done). Representing the size allows applications to determine whether they should fetch the content automatically in advance, or refuse to fetch it at all. The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference.
|
hash | Σ | 0..1 | base64Binary | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.hash Hash of the data (sha-1, base64ed) DefinitionThe calculated hash of the data using SHA-1. Represented using base64. Included so that applications can verify that the contents of a location have not changed due to technical failures (e.g., storage rot, transport glitch, incorrect version). The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see Provenance.signature for mechanism to protect a resource with a digital signature.
|
title | S Σ | 0..1 | string | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.title Label to display in place of the data DefinitionA label or set of text to display in place of the data. Applications need a label to display to a human user in place of the actual data if the data cannot be rendered or perceived by the viewer. Note that FHIR strings SHALL NOT exceed 1MB in size
General Official Corporate Logo Mappings
|
creation | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.creation Date attachment was first created DefinitionThe date that the attachment was first created. This is often tracked as an integrity issue for use of the attachment.
|
format | Σ | 0..1 | CodingBinding | There are no (further) constraints on this element Element IdDocumentReference.content.format Format/content rules for the document DefinitionAn identifier of the document encoding, structure, and template that the document conforms to beyond the base format indicated in the mimeType. Note that while IHE mostly issues URNs for format types, not all documents can be identified by a URI. Document Format Codes. DocumentReferenceFormatCodeSet (preferred)Constraints
|
context | S Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element IdDocumentReference.context Clinical context of document DefinitionThe clinical context in which the document was prepared. These values are primarily added to help with searching for interesting/relevant documents.
|
encounter | I | 0..* | Reference(Encounter | EpisodeOfCare) | There are no (further) constraints on this element Element IdDocumentReference.context.encounter Context of the document content DefinitionDescribes the clinical encounter or type of care that the document content is associated with. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Encounter | EpisodeOfCare) Constraints
|
event | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdDocumentReference.context.event Main clinical acts documented DefinitionThis list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the type Code, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act. An event can further specialize the act inherent in the type, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more event codes are included, they shall not conflict with the values inherent in the class or type elements as such a conflict would create an ambiguous situation. This list of codes represents the main clinical acts being documented. v3.ActCode (example)Constraints
| |
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdDocumentReference.context.period Time of service that is being documented DefinitionThe time period over which the service that is described by the document was provided. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
facilityType | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdDocumentReference.context.facilityType Kind of facility where patient was seen DefinitionThe kind of facility where the patient was seen. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. XDS Facility Type. FacilityTypeCodeValueSet (example)Constraints
| |
practiceSetting | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdDocumentReference.context.practiceSetting Additional details about where the content was created (e.g. clinical specialty) DefinitionThis property may convey specifics about the practice setting where the content was created, often reflecting the clinical specialty. This is an important piece of metadata that providers often rely upon to quickly sort and/or filter out to find specific content. This element should be based on a coarse classification system for the class of specialty practice. Recommend the use of the classification system for Practice Setting, such as that described by the Subject Matter Domain in LOINC. Additional details about where the content was created (e.g. clinical specialty). PracticeSettingCodeValueSet (example)Constraints
| |
sourcePatientInfo | I | 0..1 | Reference(Patient) | There are no (further) constraints on this element Element IdDocumentReference.context.sourcePatientInfo Patient demographics from source DefinitionThe Patient Information as known when the document was published. May be a reference to a version specific, or contained. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
related | S I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element IdDocumentReference.context.related Related identifiers or resources DefinitionRelated identifiers or resources associated with the DocumentReference. May be identifiers or resources that caused the DocumentReference or referenced Document to be created.
|
Hinweise
FHIR-Element | Erklärung |
---|---|
DocumentReference.id | Must-support, jedoch optional |
DocumentReference.meta | Must-support, jedoch optional |
DocumentReference.meta.profile | Verpflichtend für die Abfrage im DIZ-Repository inkl. Versionsnummer des Profils. Siehe CapabilityStatement. In allen anderen Fällen optional. |
DocumentReference.content.attachment.url | Diese absolute URL sollte auf einen Binary-Endpunkt eines FHIR-Servers verweisen. Die Hinweise der FHIR-Kernspezifikation zum Abruf von Binary-Ressourcen sind zu beachten. |
DocumentReference.content.attachment.title | Der Titel sollte eine sinnvolle menschenlesbare Beschreibung enthalten, das Element sollte nicht für den Dateinamen verwendet werden. |
DocumentReference.custodian | Sollte der Standort nicht als Organization-Ressource verfügbar sein, kann auch ggf. Reference.display oder Referenz.identifier verwendet werden. |
DocumentReference.author | Sollte der Author nicht als Practitioner-Ressource verfügbar sein, kann auch ggf. Reference.display oder Referenz.identifier verwendet werden. |
DocumentReference.context.related | Angabe des Studienkontexts |
Mapping
FHIR Element | Logischer Datensatz |
---|---|
DocumentReference.content.attachment.url | Forschungsvorhaben.Publikation.url |
DocumentReference.content.attachment.title | Forschungsvorhaben.Publikation.Titel |
DocumentReference.author | Forschungsvorhaben.Publikation.Autor |
FHIR Element | Logischer Datensatz |
---|---|
DocumentReference.content.attachment.title | Forschungsvorhaben.Datennutzungsantrag.Dokument.Name |
DocumentReference.author | Forschungsvorhaben.Datennutzungsantrag.Dokument.Autor |
DocumentReference.content.attachment.contentType | Forschungsvorhaben.Datennutzungsantrag.Dokument.Dateityp |
DocumentReference.custodian | Forschungsvorhaben.Datennutzungsantrag.Dokument.Standort |
DocumentReference.content.attachment.size | Forschungsvorhaben.Datennutzungsantrag.Dokument.Dateigroesse |
DocumentReference.content.attachment.url | Forschungsvorhaben.Datennutzungsantrag.Dokument.url |
Snapshot
DocumentReference | I | DocumentReference | There are no (further) constraints on this element Element IdDocumentReference A reference to a document DefinitionA reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text. Usually, this is used for documents other than those defined by FHIR.
| |
masterIdentifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdDocumentReference.masterIdentifier Master Version Specific Identifier DefinitionDocument identifier as assigned by the source of the document. This identifier is specific to this version of the document. This unique identifier may be used elsewhere to identify this version of the document. The structure and format of this Id shall be consistent with the specification corresponding to the formatCode attribute. (e.g. for a DICOM standard document a 64-character numeric UID, for an HL7 CDA format a serialization of the CDA Document Id extension and root in the form "oid^extension", where OID is a 64 digits max, and the Id is a 16 UTF-8 char max. If the OID is coded without the extension then the '^' character shall not be included.). CDA Document Id extension and root.
|
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element IdDocumentReference.identifier Other identifiers for the document DefinitionOther identifiers associated with the document, including version independent identifiers.
|
status | S Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element IdDocumentReference.status current | superseded | entered-in-error DefinitionThe status of this document reference. This is the status of the DocumentReference object, which might be independent from the docStatus element. This element is labeled as a modifier because the status contains the codes that mark the document or reference as not currently valid. The status of the document reference. DocumentReferenceStatus (required)Constraints
|
docStatus | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdDocumentReference.docStatus preliminary | final | amended | entered-in-error DefinitionThe status of the underlying document. The document that is pointed to might be in various lifecycle states. Status of the underlying document. CompositionStatus (required)Constraints
|
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdDocumentReference.type Kind of document (LOINC if possible) DefinitionSpecifies the particular kind of document referenced (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the document referenced. Key metadata element describing the document that describes he exact type of document. Helps humans to assess whether the document is of interest when viewing a list of documents. Precise type of clinical document. DocumentTypeValueSet (preferred)Constraints
|
category | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdDocumentReference.category Categorization of document Alternate namesclaxs DefinitionA categorization for the type of document referenced - helps for indexing and searching. This may be implied by or derived from the code specified in the DocumentReference.type. Key metadata element describing the the category or classification of the document. This is a broader perspective that groups similar documents based on how they would be used. This is a primary key used in searching. High-level kind of a clinical document at a macro level. DocumentClassValueSet (example)Constraints
|
subject | Σ I | 0..1 | Reference(Patient | Practitioner | Group | Device) | There are no (further) constraints on this element Element IdDocumentReference.subject Who/what is the subject of the document DefinitionWho or what the document is about. The document can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of farm animals, or a set of patients that share a common exposure). References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Patient | Practitioner | Group | Device) Constraints
|
date | Σ | 0..1 | instant | There are no (further) constraints on this element Element IdDocumentReference.date When this document reference was created Alternate namesindexed DefinitionWhen the document reference was created. Referencing/indexing time is used for tracking, organizing versions and searching.
|
author | S Σ I | 0..* | Reference(Practitioner | PractitionerRole | Organization | Device | Patient | RelatedPerson) | There are no (further) constraints on this element Element IdDocumentReference.author Who and/or what authored the document DefinitionIdentifies who is responsible for adding the information to the document. Not necessarily who did the actual data entry (i.e. typist) or who was the source (informant). Reference(Practitioner | PractitionerRole | Organization | Device | Patient | RelatedPerson) Constraints
|
authenticator | I | 0..1 | Reference(Practitioner | PractitionerRole | Organization) | There are no (further) constraints on this element Element IdDocumentReference.authenticator Who/what authenticated the document DefinitionWhich person or organization authenticates that this document is valid. Represents a participant within the author institution who has legally authenticated or attested the document. Legal authentication implies that a document has been signed manually or electronically by the legal Authenticator. Reference(Practitioner | PractitionerRole | Organization) Constraints
|
custodian | S I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element IdDocumentReference.custodian Organization which maintains the document DefinitionIdentifies the organization or group who is responsible for ongoing maintenance of and access to the document. Identifies the logical organization (software system, vendor, or department) to go to find the current version, where to report issues, etc. This is different from the physical location (URL, disk drive, or server) of the document, which is the technical location of the document, which host may be delegated to the management of some other organization.
|
relatesTo | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element IdDocumentReference.relatesTo Relationships to other documents DefinitionRelationships that this document has with other document references that already exist. This element is labeled as a modifier because documents that append to other documents are incomplete on their own.
|
code | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element IdDocumentReference.relatesTo.code replaces | transforms | signs | appends DefinitionThe type of relationship that this document has with anther document. If this document appends another document, then the document cannot be fully understood without also accessing the referenced document. The type of relationship between documents. DocumentRelationshipType (required)Constraints
|
target | Σ I | 1..1 | Reference(DocumentReference) | There are no (further) constraints on this element Element IdDocumentReference.relatesTo.target Target of the relationship DefinitionThe target document of this relationship. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
description | Σ | 0..1 | string | There are no (further) constraints on this element Element IdDocumentReference.description Human-readable description DefinitionHuman-readable description of the source document. Helps humans to assess whether the document is of interest. What the document is about, a terse summary of the document.
|
securityLabel | Σ | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element IdDocumentReference.securityLabel Document security-tags DefinitionA set of Security-Tag codes specifying the level of privacy/security of the Document. Note that DocumentReference.meta.security contains the security labels of the "reference" to the document, while DocumentReference.securityLabel contains a snapshot of the security labels on the document the reference refers to. Use of the Health Care Privacy/Security Classification (HCS) system of security-tag use is recommended. The confidentiality codes can carry multiple vocabulary items. HL7 has developed an understanding of security and privacy tags that might be desirable in a Document Sharing environment, called HL7 Healthcare Privacy and Security Classification System (HCS). The following specification is recommended but not mandated, as the vocabulary bindings are an administrative domain responsibility. The use of this method is up to the policy domain such as the XDS Affinity Domain or other Trust Domain where all parties including sender and recipients are trusted to appropriately tag and enforce. In the HL7 Healthcare Privacy and Security Classification (HCS) there are code systems specific to Confidentiality, Sensitivity, Integrity, and Handling Caveats. Some values would come from a local vocabulary as they are related to workflow roles and special projects. Security Labels from the Healthcare Privacy and Security Classification System. All Security Labels (extensible)Constraints
|
content | S Σ | 1..* | BackboneElement | There are no (further) constraints on this element Element IdDocumentReference.content Document referenced DefinitionThe document and format referenced. There may be multiple content element repetitions, each with a different format.
|
attachment | S Σ I | 1..1 | Attachment | There are no (further) constraints on this element Element IdDocumentReference.content.attachment Where to access the document DefinitionThe document or URL of the document along with critical metadata to prove content has integrity. When providing a summary view (for example with Observation.value[x]) Attachment should be represented with a brief display text such as "Signed Procedure Consent".
|
contentType | S Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.contentType Mime type of the content, with charset etc. DefinitionIdentifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate. Processors of the data need to be able to know how to interpret the data. Note that FHIR strings SHALL NOT exceed 1MB in size The mime type of an attachment. Any valid mime type is allowed. Mime Types (required)Constraints
General text/plain; charset=UTF-8, image/png Mappings
|
language | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.language Human language of the content (BCP-47) DefinitionThe human language of the content. The value can be any valid value according to BCP 47. Users need to be able to choose between the languages in a set of attachments. Note that FHIR strings SHALL NOT exceed 1MB in size A human language. CommonLanguages (preferred)Constraints
General en-AU Mappings
|
data | 0..1 | base64Binary | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.data Data inline, base64ed DefinitionThe actual data of the attachment - a sequence of bytes, base64 encoded. The data needs to able to be transmitted inline. The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON.
| |
url | S Σ | 1..1 | url | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.url Uri where the data can be found DefinitionA location where the data can be accessed. The data needs to be transmitted by reference. If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.
General http://www.acme.com/logo-small.png Mappings
|
size | S Σ | 0..1 | unsignedInt | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.size Number of bytes of content (if url provided) DefinitionThe number of bytes of data that make up this attachment (before base64 encoding, if that is done). Representing the size allows applications to determine whether they should fetch the content automatically in advance, or refuse to fetch it at all. The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference.
|
hash | Σ | 0..1 | base64Binary | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.hash Hash of the data (sha-1, base64ed) DefinitionThe calculated hash of the data using SHA-1. Represented using base64. Included so that applications can verify that the contents of a location have not changed due to technical failures (e.g., storage rot, transport glitch, incorrect version). The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see Provenance.signature for mechanism to protect a resource with a digital signature.
|
title | S Σ | 0..1 | string | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.title Label to display in place of the data DefinitionA label or set of text to display in place of the data. Applications need a label to display to a human user in place of the actual data if the data cannot be rendered or perceived by the viewer. Note that FHIR strings SHALL NOT exceed 1MB in size
General Official Corporate Logo Mappings
|
creation | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element IdDocumentReference.content.attachment.creation Date attachment was first created DefinitionThe date that the attachment was first created. This is often tracked as an integrity issue for use of the attachment.
|
format | Σ | 0..1 | CodingBinding | There are no (further) constraints on this element Element IdDocumentReference.content.format Format/content rules for the document DefinitionAn identifier of the document encoding, structure, and template that the document conforms to beyond the base format indicated in the mimeType. Note that while IHE mostly issues URNs for format types, not all documents can be identified by a URI. Document Format Codes. DocumentReferenceFormatCodeSet (preferred)Constraints
|
context | S Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element IdDocumentReference.context Clinical context of document DefinitionThe clinical context in which the document was prepared. These values are primarily added to help with searching for interesting/relevant documents.
|
encounter | I | 0..* | Reference(Encounter | EpisodeOfCare) | There are no (further) constraints on this element Element IdDocumentReference.context.encounter Context of the document content DefinitionDescribes the clinical encounter or type of care that the document content is associated with. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Encounter | EpisodeOfCare) Constraints
|
event | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdDocumentReference.context.event Main clinical acts documented DefinitionThis list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the type Code, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act. An event can further specialize the act inherent in the type, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more event codes are included, they shall not conflict with the values inherent in the class or type elements as such a conflict would create an ambiguous situation. This list of codes represents the main clinical acts being documented. v3.ActCode (example)Constraints
| |
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdDocumentReference.context.period Time of service that is being documented DefinitionThe time period over which the service that is described by the document was provided. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
facilityType | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdDocumentReference.context.facilityType Kind of facility where patient was seen DefinitionThe kind of facility where the patient was seen. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. XDS Facility Type. FacilityTypeCodeValueSet (example)Constraints
| |
practiceSetting | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdDocumentReference.context.practiceSetting Additional details about where the content was created (e.g. clinical specialty) DefinitionThis property may convey specifics about the practice setting where the content was created, often reflecting the clinical specialty. This is an important piece of metadata that providers often rely upon to quickly sort and/or filter out to find specific content. This element should be based on a coarse classification system for the class of specialty practice. Recommend the use of the classification system for Practice Setting, such as that described by the Subject Matter Domain in LOINC. Additional details about where the content was created (e.g. clinical specialty). PracticeSettingCodeValueSet (example)Constraints
| |
sourcePatientInfo | I | 0..1 | Reference(Patient) | There are no (further) constraints on this element Element IdDocumentReference.context.sourcePatientInfo Patient demographics from source DefinitionThe Patient Information as known when the document was published. May be a reference to a version specific, or contained. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
related | S I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element IdDocumentReference.context.related Related identifiers or resources DefinitionRelated identifiers or resources associated with the DocumentReference. May be identifiers or resources that caused the DocumentReference or referenced Document to be created.
|
Suchparameter
Folgende Suchparameter sind für das Modul Studie relevant, auch in Kombination:
Der Suchparameter "_id" MUSS unterstützt werden:
Beispiele:
GET [base]/DocumentReference?_id=103270
Anwendungshinweise: Weitere Informationen zur Suche nach "_id" finden sich in der FHIR-Basisspezifikation - Abschnitt "Parameters for all resources".
Der Suchparameter "_profile" MUSS unterstützt werden:
Beispiele:
GET [base]/DocumentReference?_profile=https://www.medizininformatik-initiative.de/fhir/modul-studie/StructureDefinition/mii-pr-studie-dokument
Anwendungshinweise: Weitere Informationen zur Suche nach "_profile" finden sich in der FHIR-Basisspezifikation - Abschnitt "Parameters for all resources".
Der Suchparameter "author" MUSS unterstützt werden:
Beispiele
GET [base]/DocumentReference?author=Practitioner/practitioner-test
Anwendungshinweise: Weitere Informationen zur Suche nach "DocumentReference.author" finden sich in der FHIR-Basisspezifikation - Abschnitt "reference".
Der Suchparameter "custodian" MUSS unterstützt werden:
Beispiele
GET [base]/DocumentReference?custodian=Organization/organization-test
Anwendungshinweise: Weitere Informationen zur Suche nach "DocumentReference.custodian" finden sich in der FHIR-Basisspezifikation - Abschnitt "reference".
Der Suchparameter "status" MUSS unterstützt werden:
Beispiele
GET [base]/DocumentReference?status=current
Anwendungshinweise: Weitere Informationen zur Suche nach "PractitionerRole.status" finden sich in der FHIR-Basisspezifikation - Abschnitt "token".
Der Suchparameter "location" MUSS unterstützt werden:
Beispiele
GET [base]/DocumentReference?location=https://example.com/fhir/Binary/document
Anwendungshinweise: Weitere Informationen zur Suche nach "DocumentReference.content.attachment.url" finden sich in der FHIR-Basisspezifikation - Abschnitt "uri".
Der Suchparameter "contenttype" MUSS unterstützt werden:
Beispiele
GET [base]/DocumentReference?contenttype=application/pdf
Anwendungshinweise: Weitere Informationen zur Suche nach "DocumentReference.content.attachment.contentType" finden sich in der FHIR-Basisspezifikation - Abschnitt "token".
Der Suchparameter "title" MUSS unterstützt werden:
Beispiele:
GET [base]/DocumentReference?title=Beispiel Dokument
Anwendungshinweise: Weitere Informationen zur Suche nach "DocumentReference.content.attachment.title" finden sich in der FHIR-Basisspezifikation - Abschnitt "String Search".
Der Suchparameter "size" MUSS unterstützt werden:
Beispiele:
GET [base]/DocumentReference?size=1000
Anwendungshinweise: Weitere Informationen zur Suche nach "DocumentReference.content.attachment.size" finden sich in der FHIR-Basisspezifikation - Abschnitt "Number Search".
Der Suchparameter "related" MUSS unterstützt werden:
Beispiele:
GET [base]/DocumentReference?related=ResearchStudy/example
Anwendungshinweise: Weitere Informationen zur Suche nach "DocumentReference.context.related" finden sich in der FHIR-Basisspezifikation - Abschnitt "reference".
Beispiele
Beispiel (minimal):
{ "resourceType": "DocumentReference", "id": "mii-exa-studie-dokument", "meta": { "profile": [ "https://www.medizininformatik-initiative.de/fhir/modul-studie/StructureDefinition/mii-pr-studie-dokument" ] }, "status": "current", "content": [ { "attachment": { "url": "https://example.com/fhir/Binary/document", "title": "Beispiel Dokument", "contentType": "application/pdf", "size": 2000 } } ], "author": [ { "reference": "Organization/Example" } ], "custodian": { "reference": "Organization/Example" }, "context": { "related": [ { "reference": "ResearchStudy/Example" } ] } }
Powered by SIMPLIFIER.NET