Intersection of http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference and http://hl7.org/fhir/us/spl/StructureDefinition/SPLDocumentReference

This is the set of resources that conform to both US Core DocumentReference Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference) and SPLDocumentReference (http://hl7.org/fhir/us/spl/StructureDefinition/SPLDocumentReference).

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. DocumentReference 0..*A reference to a document
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: ?? (required): IETF language tag for a human language
Additional BindingsPurpose
??Starter
... contained 0..*ResourceContained, inline Resources
... extension 0..*Extensionleft: Additional content defined by implementations; right: Extension
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier SΣ1..*Identifierleft: Other identifiers for the document; right: Business identifiers for the document
... status ?!SΣ1..1codecurrent | superseded | entered-in-error
Binding: ?? (required): The status of the document reference.
... docStatus Σ0..1codeleft: preliminary | final | amended | entered-in-error; right: registered | partial | preliminary | final | amended | corrected | appended | cancelled | entered-in-error | deprecated | unknown
Binding Description: (required) ⚠: Status of the underlying document.
... type SΣ1..1CodeableConceptKind of document (LOINC if possible)
Binding: ?? (required): All LOINC values whose SCALE is "Doc" in the LOINC database and the HL7 v3 Code System NullFlavor concept 'unknown'
Additional BindingsPurpose
??Min Binding
... category SΣ1..*CodeableConceptCategorization of document
Binding: ?? (example): High-level kind of a clinical document at a macro level.
... subject SΣ1..1Reference(US Core Patient Profile S | Practitioner | Group | Device)Who/what is the subject of the document
... date SΣ1..1instantWhen this document reference was created
... author SΣ0..*Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | US Core PractitionerRole Profile | US Core RelatedPerson Profile | Device)Who and/or what authored the document
... custodian 0..1Reference(Organization)Organization which maintains the document
... relatesTo Σ0..*BackboneElementRelationships to other documents
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... code Σ1..1codeleft: replaces | transforms | signs | appends; right: The relationship type with another document
Binding Description: (required) ⚠: left: The type of relationship between documents.; right: The type of relationship between the documents.
.... target Σ1..1Reference(DocumentReference)Target of the relationship
... description Σ0..1stringHuman-readable description
... securityLabel Σ0..*CodeableConceptDocument security-tags
Binding: ?? (extensible): Security Labels from the Healthcare Privacy and Security Classification System.
... content SΣ1..*BackboneElementDocument referenced
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... attachment SΣC1..1AttachmentWhere to access the document
Constraints: us-core-6
..... extension 0..*ExtensionAdditional content defined by implementations
..... contentType SΣ0..1codeMime type of the content, with charset etc.
Binding Description: (required) ⚠: left: The mime type of an attachment. Any valid mime type is allowed.; right: BCP 13 (RFCs 2045, 2046, 2047, 4288, 4289 and 2049)
Example General: text/plain; charset=UTF-8, image/png
..... language Σ0..1codeHuman language of the content (BCP-47)
Binding: ?? (required): IETF language tag for a human language.
Additional BindingsPurpose
??Starter

Example General: en-AU
..... data S1..1base64BinaryData inline, base64ed
..... url SΣ0..1urlUri where the data can be found
Example General: http://www.acme.com/logo-small.png
..... size Σ0..1unsignedIntNumber of bytes of content (if url provided)
..... hash Σ0..1base64BinaryHash of the data (sha-1, base64ed)
..... title Σ0..1stringLabel to display in place of the data
Example General: Official Corporate Logo
..... creation Σ0..1dateTimeDate attachment was first created
... context SΣ0..1BackboneElementleft: Clinical context of document; right: Context of the document content

doco Documentation for this format