## Profile Comparison between https://profiles.ihe.net/ITI/MHD/StructureDefinition/IHE.MHD.SimplifiedPublish.DocumentReference vs https://profiles.ihe.net/ITI/MHD/StructureDefinition/IHE.MHD.SimplifiedPublish.DocumentReference

Left: | MHD DocumentReference for Simplified Publish (https://profiles.ihe.net/ITI/MHD/StructureDefinition/IHE.MHD.SimplifiedPublish.DocumentReference)
Right: | MHD DocumentReference for Simplified Publish (https://profiles.ihe.net/ITI/MHD/StructureDefinition/IHE.MHD.SimplifiedPublish.DocumentReference)

### Messages

Error | StructureDefinition.version | Values for version differ: '5.0.0' vs '4.2.4-current'
Information | StructureDefinition.date | Values for date differ: '2025-12-18T09:48:18-06:00' vs '2026-01-13T00:00:58+00:00'
Warning | StructureDefinition.fhirVersion | Values for fhirVersion differ: '5.0.0' vs '4.0.1'
Information | StructureDefinition.definition | Values for definition differ: 'A reference to a document of any kind for any purpose. While the term “document” implies a more narrow focus, for this resource this 'document' encompasses *any* serialized object with a mime-type, it includes formal patient-centric documents (CDA), clinical notes, scanned paper, non-patient specific documents like policy text, as well as a photo, video, or audio recording acquired or used in healthcare. The DocumentReference resource provides metadata about the document so that the document can be discovered and managed. The actual content may be inline base64 encoded data or provided by direct reference.' vs 'A 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.'
Information | StructureDefinition.comment | Values for comment differ: 'Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.' vs 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.'
Information | StructureDefinition.comment | Values for comment differ: 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.' vs 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.'
Information | StructureDefinition.comment | Values for comment differ: 'Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'
Information | StructureDefinition.definition | Values for definition differ: 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.' vs 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.'
Information | StructureDefinition.comment | Values for comment differ: 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.' vs 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.'
Information | StructureDefinition.short | Values for short differ: 'Extension' vs 'Additional content defined by implementations'
Information | StructureDefinition.definition | Values for definition differ: 'An Extension' vs 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
Information | StructureDefinition.short | Values for short differ: 'Business identifiers for the document' vs 'Other identifiers for the document'
Information | StructureDefinition.definition | Values for definition differ: 'Other business identifiers associated with the document, including version independent identifiers.' vs 'Other identifiers associated with the document, including version independent identifiers.'
Warning | DocumentReference.identifier | Elements differ in definition for mustSupport: 'true' vs 'false'
Information | DocumentReference.identifier | Element maximum cardinalities differ: '1' vs '2147483647'
Information | StructureDefinition.short | Values for short differ: 'registered | partial | preliminary | final | amended | corrected | appended | cancelled | entered-in-error | deprecated | unknown' vs 'preliminary | final | amended | entered-in-error'
Information | DocumentReference.type | Example/preferred bindings differ at DocumentReference.type using binding from SimplifiedPublishDocumentReference
Information | StructureDefinition.short | Values for short differ: 'Context of the document content' vs 'Clinical context of document'
Information | StructureDefinition.definition | Values for definition differ: 'Describes the clinical encounter or type of care that the document content is associated with.' vs 'The clinical context in which the document was prepared.'
Information | DocumentReference.context | Element maximum cardinalities differ: '2147483647' vs '1'
Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).'
Information | StructureDefinition.short | Values for short differ: 'The relationship type with another document' vs 'replaces | transforms | signs | appends'
Information | StructureDefinition.definition | Values for definition differ: 'A set of Security-Tag codes specifying the level of privacy/security of the Document found at DocumentReference.content.attachment.url. Note that DocumentReference.meta.security contains the security labels of the data elements in DocumentReference, while DocumentReference.securityLabel contains the security labels for the document the reference refers to. The distinction recognizes that the document may contain sensitive information, while the DocumentReference is metadata about the document and thus might not be as sensitive as the document. For example: a psychotherapy episode may contain highly sensitive information, while the metadata may simply indicate that some episode happened.' vs 'A 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.'
Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).'
Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
Information | StructureDefinition.comment | Values for comment differ: '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](http://hl7.org/fhir/R5/provenance-definitions.html#Provenance.signature) for mechanism to protect a resource with a digital signature.' vs '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](http://hl7.org/fhir/R4/provenance-definitions.html#Provenance.signature) for mechanism to protect a resource with a digital signature.'

### Metadata

Name | Value | Comments
--- | --- | ---
abstract | false |
baseDefinition | http://hl7.org/fhir/StructureDefinition/DocumentReference |
copyright |  |
date | 2025-12-18T09:48:18-06:00 | 2026-01-13T00:00:58+00:00 | Values Differ
description | A 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 |
experimental |  |
fhirVersion | 5.0.0 | 4.0.1 | Values Differ
jurisdiction |  |
jurisdiction[0] | http://unstats.un.org/unsd/methods/m49/m49.htm#001 |
kind | resource |
name | SimplifiedPublishDocumentReference |
publisher | IHE IT Infrastructure Technical Committee |
purpose |  |
status | active |
title | MHD DocumentReference for Simplified Publish |
type | DocumentReference |
url | https://profiles.ihe.net/ITI/MHD/StructureDefinition/IHE.MHD.SimplifiedPublish.DocumentReference |
version | 5.0.0 | 4.2.4-current | Values Differ

### Structure

Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments
--- | --- | --- | --- | --- | --- | --- | --- | --- | ---
DocumentReference | C | 0..* | DocumentReference | A reference to a document |  | 0..* | DocumentReference | A reference to a document |
id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact |
meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource |
implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created |
language |  | 0..1 | code | Language of the resource content Binding: ?? (required): IETF language tag for a human language
Additional Bindings | Purpose
?? | Starter
|  | 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
Additional Bindings | Purpose
?? | Max Binding
text |  | 0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements |  | 0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements |
contained |  | 0..* | Resource | Contained, inline Resources |  | 0..* | Resource | Contained, inline Resources |
Slices for extension |  | 0..* | Extension | Extension Slice: Unordered, Open by value:url |  | 0..* | Extension | Additional content defined by implementations |
modifierExtension | ?!Σ | 0..0 |  | Extension | ?! | 0..0 |  | Extension |
Slices for identifier | S Σ | 1..1 | Identifier | Business identifiers for the document Slice: Unordered, Open by value:use | Σ | 1..* | Identifier | Other identifiers for the document Slice: Unordered, Open by value:type | Elements differ in definition for mustSupport: 'true' vs 'false' Element maximum cardinalities differ: '1' vs '2147483647'
version | Σ | 0..1 | string | An explicitly assigned identifer of a variation of the content in the DocumentReference |  |  |  |  | Removed this element
basedOn |  | 0..* | Reference(Appointment | AppointmentResponse | CarePlan | Claim | CommunicationRequest | Contract | CoverageEligibilityRequest | DeviceRequest | EnrollmentRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | RequestOrchestration | ServiceRequest | SupplyRequest | VisionPrescription) | Procedure that caused this media to be created |  |  |  |  | Removed this element
status | ?!Σ | 1..1 | code | current | superseded | entered-in-error Binding: ?? (required): The status of the document reference. Required Pattern: current | ?!Σ | 1..1 | code | current | superseded | entered-in-error Binding: ?? (required): The status of the document reference. Required Pattern: current |
docStatus | Σ | 0..0 |  | registered | partial | preliminary | final | amended | corrected | appended | cancelled | entered-in-error | deprecated | unknown Binding: ?? (required): Status of the underlying document. | Σ | 0..0 |  | preliminary | final | amended | entered-in-error Binding: ?? (required): Status of the underlying document. |
modality | Σ | 0..* | CodeableConcept | Imaging modality used Binding: ?? (extensible): Type of acquired data in the instance. |  |  |  |  | Removed this element
type | S Σ | 0..1 | CodeableConcept | Kind of document (LOINC if possible) Binding: ?? (preferred): Precise type of clinical document. | S Σ | 0..1 | CodeableConcept | Kind of document (LOINC if possible) Binding: ?? (preferred): Precise type of clinical document. | Example/preferred bindings differ at DocumentReference.type using binding from SimplifiedPublishDocumentReference
category | S Σ | 0..1 | CodeableConcept | Categorization of document Binding: ?? (example): High-level kind of document at a macro level. | S Σ | 0..1 | CodeableConcept | Categorization of document Binding: ?? (example): High-level kind of a clinical document at a macro level. |
subject | Σ | 1..1 | Reference(Patient) | Who/what is the subject of the document | Σ | 1..1 | Reference(Patient) | Who/what is the subject of the document |
context | C | 0..* | Reference(Appointment | Encounter | EpisodeOfCare) | Context of the document content | Σ | 0..1 | BackboneElement | Clinical context of document | Element maximum cardinalities differ: '2147483647' vs '1'
id |  |  |  |  |  | 0..1 | string | Unique id for inter-element referencing | Added this element
extension |  |  |  |  |  | 0..* | Extension | Additional content defined by implementations | Added this element
modifierExtension |  |  |  |  | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | Added this element
encounter |  |  |  |  |  | 0..* | Reference(Encounter | EpisodeOfCare) | Context of the document content | Added this element
event |  |  |  |  |  | 0..* | CodeableConcept | Main clinical acts documented Binding: ?? (example): This list of codes represents the main clinical acts being documented. | Added this element
period |  |  |  |  | S Σ | 0..1 | Period | Time of service that is being documented | Added this element
facilityType |  |  |  |  | S | 0..1 | CodeableConcept | Kind of facility where patient was seen Binding: ?? (example): XDS Facility Type. | Added this element
practiceSetting |  |  |  |  | S | 0..1 | CodeableConcept | Additional details about where the content was created (e.g. clinical specialty) Binding: ?? (example): Additional details about where the content was created (e.g. clinical specialty). | Added this element
sourcePatientInfo |  |  |  |  | S | 0..1 | Reference(Patient) | Patient demographics from source | Added this element
related |  |  |  |  |  | 0..* | Reference(Resource) | Related identifiers or resources | Added this element
event |  | 0..* | CodeableReference() | Main clinical acts documented Binding: ?? (example): This list of codes represents the main clinical acts being documented. |  |  |  |  | Removed this element
bodySite | Σ | 0..* | CodeableReference(BodyStructure) | Body part included Binding: ?? (example): SNOMED CT Body site concepts |  |  |  |  | Removed this element
facilityType | S C | 0..1 | CodeableConcept | Kind of facility where patient was seen Binding: ?? (example): XDS Facility Type. |  |  |  |  | Removed this element
practiceSetting | S C | 0..1 | CodeableConcept | Additional details about where the content was created (e.g. clinical specialty) Binding: ?? (example): Additional details about where the content was created (e.g. clinical specialty). |  |  |  |  | Removed this element
period | S Σ | 0..1 | Period | Time of service that is being documented |  |  |  |  | Removed this element
date | S Σ | 0..1 | instant | When this document reference was created | S Σ | 0..1 | instant | When this document reference was created |
author | S Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | Device | Patient | RelatedPerson | CareTeam) | Who and/or what authored the document | S Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | Device | Patient | RelatedPerson) | Who and/or what authored the document |
attester |  | 0..1 | BackboneElement | Attests to accuracy of the document |  |  |  |  | Removed this element
custodian |  | 0..1 | Reference(Organization) | Organization which maintains the document |  | 0..1 | Reference(Organization) | Organization which maintains the document |
relatesTo | S Σ | 0..* | BackboneElement | Relationships to other documents | S Σ | 0..* | BackboneElement | Relationships to other documents |
id |  | 0..1 | string | Unique id for inter-element referencing |  | 0..1 | string | Unique id for inter-element referencing |
extension |  | 0..* | Extension | Additional content defined by implementations |  | 0..* | Extension | Additional content defined by implementations |
modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
code | Σ | 1..1 | CodeableConcept | The relationship type with another document Binding: ?? (extensible): The type of relationship between the documents. | Σ | 1..1 | code | replaces | transforms | signs | appends Binding: ?? (required): The type of relationship between documents. |
target | Σ | 1..1 | Reference(DocumentReference) | Target of the relationship | Σ | 1..1 | Reference(DocumentReference) | Target of the relationship |
description | Σ | 0..1 | markdown | Human-readable description | Σ | 0..1 | string | Human-readable description |
securityLabel | S Σ | 0..* | CodeableConcept | Document security-tags Binding: ?? (example): Example Security Labels from the Healthcare Privacy and Security Classification System. | S Σ | 0..* | CodeableConcept | Document security-tags Binding: ?? (extensible): Security Labels from the Healthcare Privacy and Security Classification System. |
content | Σ | 1..1 | BackboneElement | Document referenced | Σ | 1..1 | BackboneElement | Document referenced |
id |  | 0..1 | string | Unique id for inter-element referencing |  | 0..1 | string | Unique id for inter-element referencing |
extension |  | 0..* | Extension | Additional content defined by implementations |  | 0..* | Extension | Additional content defined by implementations |
modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
attachment | Σ | 1..1 | Attachment | Where to access the document | Σ | 1..1 | Attachment | Where to access the document |
id |  | 0..1 | id | Unique id for inter-element referencing |  | 0..1 | string | Unique id for inter-element referencing |
Slices for extension |  | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url |  | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url |
contentType | Σ C | 1..1 | code | Mime type of the content, with charset etc. Binding: ?? (required): BCP 13 (RFCs 2045, 2046, 2047, 4288, 4289 and 2049) Example General: text/plain; charset=UTF-8, image/png | Σ | 1..1 | code | Mime type of the content, with charset etc. Binding: ?? (required): The mime type of an attachment. Any valid mime type is allowed. Example General: text/plain; charset=UTF-8, image/png |
language | S Σ | 0..1 | code | Human language of the content (BCP-47) Binding: ?? (required): IETF language tag for a human language.
Additional Bindings | Purpose
?? | Starter
Example General: en-AU | S Σ | 0..1 | code | Human language of the content (BCP-47) Binding: ?? (preferred): A human language.
Additional Bindings | Purpose
?? | Max Binding
Example General: en-AU |
data | C | 1..1 | base64Binary | The document is contained in the .data element, base64 encoded |  | 1..1 | base64Binary | The document is contained in the .data element, base64 encoded |
url | Σ | 0..0 |  | Uri where the data can be found Example General: http://www.acme.com/logo-small.png | Σ | 0..0 |  | Uri where the data can be found Example General: http://www.acme.com/logo-small.png |
size | Σ | 0..1 | integer64 | Number of bytes of content (if url provided) | Σ | 0..1 | unsignedInt | Number of bytes of content (if url provided) |
hash | Σ | 0..1 | base64Binary | Hash of the data (sha-1, base64ed) | Σ | 0..1 | base64Binary | Hash of the data (sha-1, base64ed) |
title | Σ | 0..1 | string | Label to display in place of the data Example General: Official Corporate Logo | Σ | 0..1 | string | Label to display in place of the data Example General: Official Corporate Logo |
creation | S Σ | 0..1 | dateTime | Date attachment was first created | S Σ | 0..1 | dateTime | Date attachment was first created |
height |  | 0..1 | positiveInt | Height of the image in pixels (photo/video) |  |  |  |  | Removed this element
width |  | 0..1 | positiveInt | Width of the image in pixels (photo/video) |  |  |  |  | Removed this element
frames |  | 0..1 | positiveInt | Number of frames if > 1 (photo) |  |  |  |  | Removed this element
duration |  | 0..1 | decimal | Length in seconds (audio / video) |  |  |  |  | Removed this element
pages |  | 0..1 | positiveInt | Number of printed pages |  |  |  |  | Removed this element
profile | S Σ | 0..1 | BackboneElement | Content profile rules for the document |  |  |  |  | Removed this element
format |  |  |  |  | S Σ | 0..1 | Coding | Format/content rules for the document Binding: ?? (preferred): Document Format Codes. | Added this element
masterIdentifier |  |  |  |  | Σ | 0..1 | Identifier | Master Version Specific Identifier | Added this element
authenticator |  |  |  |  |  | 0..1 | Reference(Practitioner | PractitionerRole | Organization) | Who/what authenticated the document | Added this element
Documentation for this format