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

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 US Core DocumentReference Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference).

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: ?? (preferred): A human language.
Additional BindingsPurpose
??Max Binding
... text 0..1NarrativeText 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..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... masterIdentifier Σ0..1IdentifierMaster Version Specific Identifier
... identifier SΣ0..*IdentifierOther identifiers for the document
... status ?!SΣ1..1codecurrent | superseded | entered-in-error
Binding: ?? (required)
... docStatus Σ0..1codepreliminary | final | amended | entered-in-error
Binding: ?? (required): Status of the underlying document.
... type SΣ1..1CodeableConceptKind of document (LOINC if possible)
Binding: ?? (required): left: All LOINC values whose SCALE is DOC in the LOINC database and the HL7 v3 Code System NullFlavor concept 'unknown'; right: All LOINC values whose SCALE is "Doc" in the LOINC database and the HL7 v3 Code System NullFlavor concept 'unknown'
... category SΣ1..*CodeableConceptCategorization of document
Binding: ?? (extensible): The US Core DocumentReferences Type Value Set is a 'starter set' of categories supported for fetching and storing clinical notes.
... subject SΣ1..1Reference(US Core Patient Profile | #sd-us-core-patient-us-core-patient)Who/what is the subject of the document
... date SΣ0..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 | RelatedPerson | Device | #sd-us-core-practitioner-us-core-practitioner)Who and/or what authored the document
... authenticator 0..1Reference(Practitioner | PractitionerRole | Organization)Who/what authenticated 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..1codereplaces | transforms | signs | appends
Binding: ?? (required): The type of relationship between 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Σ1..1codeMime 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 Σ0..1codeHuman language of the content (BCP-47)
Binding: ?? (preferred): A human language.
Additional BindingsPurpose
??Max Binding

Example General: en-AU
..... data S0..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
.... format SΣ0..1CodingFormat/content rules for the document
Binding: ?? (extensible)
... context SΣ0..1BackboneElementClinical context of document
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... encounter S0..1Reference(US Core Encounter Profile | #sd-us-core-encounter-us-core-encounter)Context of the document content
.... event 0..*CodeableConceptMain clinical acts documented
Binding: ?? (example): This list of codes represents the main clinical acts being documented.
.... period SΣ0..1PeriodTime of service that is being documented
.... facilityType 0..1CodeableConceptKind of facility where patient was seen
Binding: ?? (example): XDS Facility Type.
.... practiceSetting 0..1CodeableConceptAdditional 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).
.... sourcePatientInfo 0..1Reference(Patient)Patient demographics from source
.... related 0..*Reference(Resource)Related identifiers or resources

doco Documentation for this format