Union of http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-documentreference and http://hl7.org/fhir/ca/baseline/StructureDefinition/profile-documentreference

This is the set of resources that conform to either of the profiles IPA-DocumentReference (http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-documentreference) and DocumentReference Profile for metadata about the document (http://hl7.org/fhir/ca/baseline/StructureDefinition/profile-documentreference). E.g. what you have to deal with if you get resources conforming to one of them

Structure

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
DocumentReference		0..*		left: A reference to a document; right: DocumentReference Profile
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: ?? (preferred): A human language.
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
contained		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
masterIdentifier	SΣ	0..1	Identifier	Master Version Specific Identifier
identifier	Σ	0..*	Identifier	Other identifiers for the document
status	?!SΣ	1..1	code	current | superseded | entered-in-error Binding: ?? (required): The status of the document reference.
docStatus	Σ	0..1	code	preliminary | final | amended | entered-in-error Binding: ?? (required): Status of the underlying document.
type	SΣ	0..1	CodeableConcept	Kind of document (LOINC if possible) Binding: ?? (preferred): Precise type of clinical document.
category	SΣ	0..*	CodeableConcept	Categorization of document Binding: ?? (example): High-level kind of a clinical document at a macro level.
subject	SΣ	0..1	Reference(IPA-Patient | #sd-ipa-patient-profile-patient)	Who/what is the subject of the document
date	SΣ	0..1	instant	When this document reference was created
author	SΣ	0..*	Reference(IPA-Practitioner | IPA-PractitionerRole | Organization | Device | IPA-Patient | RelatedPerson | #sd-ipa-practitioner-profile-practitioner)	Who and/or what authored the document
authenticator	S	0..1	Reference(Practitioner | PractitionerRole | Organization)	Who/what authenticated the document
custodian	S	0..1	Reference(Organization)	Organization which maintains the document
relatesTo	Σ	0..*	BackboneElement	Relationships to other documents
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
code	Σ	1..1	code	replaces | transforms | signs | appends Binding: ?? (required): The type of relationship between documents.
target	Σ	1..1	Reference(DocumentReference)	Target of the relationship
description	Σ	0..1	string	Human-readable description
securityLabel	Σ	0..*	CodeableConcept	Document security-tags Binding: ?? (extensible): Security Labels from the Healthcare Privacy and Security Classification System.
content	SΣ	1..*	BackboneElement	Document referenced
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
attachment	SΣC	1..1	Attachment	Where to access the document Constraints: ipa-doc-1
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
contentType	SOΣ	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 Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
language	Σ	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	SO	0..1	base64Binary	Data inline, base64ed Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
url	SOΣ	0..1	url	Uri where the data can be found Example General: http://www.acme.com/logo-small.png Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
size	Σ	0..1	unsignedInt	Number of bytes of content (if url provided)
hash	Σ	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
creation	Σ	0..1	dateTime	Date attachment was first created
format	SΣ	0..1	Coding	Format/content rules for the document Binding: ?? (preferred): Document Format Codes.
context	SΣ	0..1	BackboneElement	Clinical context of document
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
encounter	S	0..*	Reference(Encounter | EpisodeOfCare)	Context of the document content
event		0..*	CodeableConcept	Main clinical acts documented Binding: ?? (example): This list of codes represents the main clinical acts being documented.
period	SΣ	0..1	Period	Time of service that is being documented
facilityType		0..1	CodeableConcept	Kind of facility where patient was seen Binding: ?? (example): XDS Facility Type.
practiceSetting	S	0..1	CodeableConcept	left: Additional details about where the content was created (e.g. clinical specialty); right: PractitionerSpecialty Binding: ?? (preferred): left: Additional details about where the content was created (e.g. clinical specialty).; right: Defines the clinical, medical, surgical or other healthcare-related service specialty of a practitioner who interacts, treats or provides such services to or for a patient.
sourcePatientInfo	S	0..1	Reference(Patient)	Patient demographics from source
related		0..*	Reference(Resource)	Related identifiers or resources
Documentation for this format