This page is part of the FHIR Specification (v0.05: DSTU 1 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

Resource DocumentHeader - Formal Definitions

The formal definitions for the elements in the documentheader resource. Also available as an XML file.

DocumentHeader
DefinitionA documentation of healthcare-related information that is assembled together into a single statement of meaning that establishes its own context. A document is composed of a set of resources that include both human and computer readable portions. A human may attest to the accuracy of the human readable portion, and may authenticate and/or sign the entire whole. A document may be kept as a set of logically linked resources, or they may be bundled together in an atom feed
Control1..1
RequirementsFor document based framework
CommentsWhile the focus of this specification is on patient-specific clinical documents, this resource can also apply to other healthcare-related documents such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical
RIM MappingDocument[classCode="DOC" and moodCode="EVN" and isNormalAct()]
To DoConfidentiality? Language? Consent? Signatures
DocumentHeader.id
DefinitionThe unique system identifier of the document
Control1..1
Typeid
Must Understandtrue
RequirementsEach document needs a unique identifier so that other documents and underlying infrastructure can reference it
CommentsMust be globally unique. UUIDs are recommended
RIM Mappingunique(./id[isNormalDatatype() and displayable="false" and scope="OBJ" and reliability="ISS"])
DocumentHeader.instant
Definitionthe document creation time, when the document first came into being. Where the CDA document is a transform from an original document in some other format, the ClinicalDocument.effectiveTime is the time the original document is created.
Control1..1
Typeinstant
Must Understandtrue
RequirementsCreation time is used for tracking, organizing versions and searching.
RIM Mapping./effectiveTime[type="TS"]
DocumentHeader.type
DefinitionSpecifying the particular kind of document (e.g. History and Physical, Discharge Summary, Progress Note)
Control1..1
TypeCodeableConcept from DocumentType
Must Understandtrue
RequirementsKey metadata element describing the document, used in searching/filtering.
RIM Mapping./code
DocumentHeader.title
DefinitionOfficial human-readable label for the document
Control0..1
Typestring
RequirementsHelps humans to assess whether the document is of interest
CommentsIt's commonly the case that clinical documents do not have a title and are collectively referred to by the display name of Document.type (e.g. a "consultation" or "progress note"). Where these display names are rendered to the clinician or where the document has a unique title, the Document.title value should be used
RIM Mapping./title
DocumentHeader.replaces
DefinitionIdentifies the document this document supersedes, if any.
Control0..1
Typeid
Must Understandtrue
RequirementsUsed to establish relationships between documents to determine which is the most current/authoritative.
RIM Mappingunique(highest(./outboundRelationship[typeCode="RPLC and isNormalActRelationship()], priorityNumber)/target[classCode="DOC" and moodCode="EVN" and isNormalAct]/id[isNormalDatatype() and displayable="false" and scope="OBJ" and reliability="ISS"])
DocumentHeader.enterer
DefinitionThe person or device that performed the data entry leading to this document. Where there is more than one candidate, pick the most proximal to the document creation or capture on a per-section basis.
Control0..1
TypeResource(Agent)
RequirementsIdentifies who is responsible for the entry of the data.
CommentsCan provide other enterers in extensions
RIM Mappingunique(highest(./participation[typeCode="INT" and isNormalParticipation], priorityNumber)/role[classCode="ASSIGNED" and isNormalRole]/player[determinerCode="INST" and classCode=("DEV", "PSN") and isNormalEntity()])
DocumentHeader.subject
DefinitionIdentifies the primary subject of the document.
Control1..1
TypeResource(Patient|Group|Device)
Must Understandtrue
RequirementsEssential metadata for searching for the document, identifies who the document applies to
CommentsFor clinical documents, this is usually the patient.
RIM Mappingunique(./participation[typeCode="SBJ" and isNormalParticipation]/role[typeCode="PAT"]) or unique(./participation[typeCode="SBJ" and isNormalParticipation]/role[typeCode="IDENT"]/player[determinerCode="INST" and classCode=("DEV", "ORG") and isNormalEntity()])
To DoNeed to extend this to support documents with other types of subjects. Also rationalize with encounter & context elements
DocumentHeader.informant
DefinitionIdentifies the source that recounted the information recorded
Control0..1
TypeResource(Person)
RequirementsProvides context as to the potential accuracy of the information
CommentsGenerally used if information is sourced from a non-clinician (patient, relative, etc.)
RIM Mappingunique(highest(./participation[typeCode="INF" and isNormalParticipation], priorityNumber)/role[classCode="ASSIGNED" and isNormalRole]/player[determinerCode="INST" and classCode=("DEV", "PSN") and isNormalEntity()])
DocumentHeader.author
DefinitionIdentifies who is responsible for the information in the document. (Not necessarily who typed it in.)
Control1..*
TypeResource(Agent)
RequirementsIdentifies who is responsible for the content.
RIM Mapping./participation[typeCode="AUT" and isNormalParticipation]/role[classCode="ASSIGNED" and isNormalRole()]
DocumentHeader.attester
DefinitionA participant who has attested to the accuracy of the document
Control0..*
RequirementsIdentifies responsibility for the accuracy of the document content.
RIM Mapping./participation[typeCode="AUTHEN" and isNormalParticipation]
DocumentHeader.attester.mode
DefinitionThe type of attestation the authenticator offers
Control1..1
Typecode from DocumentAuthenticationMode
RequirementsIndicates the level of officialness of the attestation.
RIM Mappingunique(./modeCode)
DocumentHeader.attester.time
DefinitionWhen document was attested by the party
Control0..1
TypedateTime
RequirementsIdentifies when the information in the document was deemed accurate. (Things may have changed since then.)
RIM Mapping./time[type="TS" and isNormalDatatype()]
DocumentHeader.attester.party
DefinitionWho attested the document in the specified way
Control0..1
TypeResource(Agent|Organization)
RequirementsIdentifies who has taken on the responsibility for accuracy of the document content.
RIM Mapping./role[classCode="ASSIGNED" and isNormalRole]/player[determinerCode="INST" and classCode=("DEV", "PSN") and isNormalEntity()] or ./role[classCode="ASSIGNED" and isNormalRole and not(player)]/scoper[determinerCode="INST" and classCode="ORG" and isNormalEntity()]
DocumentHeader.recipient
DefinitionIdentifies the people and organisations for whom the document is intended
Control0..*
TypeResource(Agent|Organization)
RequirementsUsed for routing and also provides context as to intended audience.
RIM Mapping./participation[typeCode="RCV" and isNormalParticipation]/role[classCode="ASSIGNED" and isNormalRole] or ./participation[typeCode="RCV" and isNormalParticipation]/role[classCode="ASSIGNED" and isNormalRole and not (player)]/scoper[classCode="ORG" and determinerCode="INST" and isNormalEntity()]
DocumentHeader.custodian
DefinitionIdentifies the organization or group who is responsible for ongoing maintenance of and access to the document.
Control1..1
TypeResource(Organization)
RequirementsIdentifies where to go to find the current version, where to report issues, etc.
RIM Mapping./participation[typeCode="RCV" and isNormalParticipation]/role[classCode="CUST" and isNormalRole and not (player)]/scoper[classCode="ORG" and determinerCode="INST" and isNormalEntity()]
DocumentHeader.context
DefinitionThe main Act, such as a colonoscopy or an appendectomy, being documented
Control0..1
TypeResource(Any)
RequirementsProvides context for the document and creates a linkage between a resource describing an event and the document created describing the event.
CommentsThe event needs to be consistent with the type element, though can provide further information if desired
RIM Mappingunique(highest(./outboundRelationship[typeCode="SUBJ" and isNormalActRelationship()], priorityNumber)/target[moodCode="EVN" and isNormalAct])
DocumentHeader.encounter
DefinitionDescribes the clinical encounter or type of care this document is associated with.
Control0..1
TypeResource(Admission|InterestOfCare)
RequirementsProvides context for the document and supports searching.
RIM Mappingunique(highest(./outboundRelationship[typeCode="SUBJ" and isNormalActRelationship()], priorityNumber)/target[moodCode="EVN" and classCode=("ENC", "PCPR") and isNormalAct])
DocumentHeader.stylesheet
DefinitionA fixed stylesheet to use when rendering the documents
Control0..1
TypeAttachment
RIM MappingN/A
DocumentHeader.representation
DefinitionAn alternative representation of the document that can be used in place of the html based rendering
Control0..1
TypeAttachment
RequirementsSupport for CDA level 1
CommentsTypically, this is application/pdf
DocumentHeader.section
DefinitionIdentifies a main topic within the document's table of contents
Control0..*
RequirementsAdds organization and human navigability to the information in the document.
RIM Mapping./outboundRelationship[typeCode="COMP" and isNormalActRelationship()]/target[moodCode="EVN" and classCode="DOCSECT" and isNormalAct]
DocumentHeader.section.type
DefinitionA code identifying the kind of content contained within the section
Control0..1
TypeCodeableConcept from DocumentSectionType
RequirementsProvides computable standardized labels to topics within the document.
RIM Mapping./code
DocumentHeader.section.instant
DefinitionIdentifies when the content of the section was created
Control0..1
Typeinstant
CommentsSections are often re-used in several documents, thus the creation time of a section may differ from that of the document
RIM Mapping./effectiveTime[type="TS" and isNormalDatatype()]
DocumentHeader.section.author
DefinitionIdentifies who is responsible for the information in the section. (Not necessarily who typed it in.)
Control0..1
TypeResource(Agent)
RequirementsIdentifies who is responsible for the content.
RIM Mapping./participation[typeCode="AUT" and isNormalParticipation]/role[classCode="ASSIGNED" and isNormalRole]/player[determinerCode="INST" and classCode=("DEV", "PSN") and isNormalEntity()]
DocumentHeader.section.enterer
DefinitionThe person or device that performed the data entry leading to this section. Where there is more than one candidate, pick the most proximal to the document creation.
Control0..1
TypeResource(Agent)
RequirementsIdentifies who is responsible for the entry of the data.
CommentsCan provide other enterers in extensions
RIM Mappingunique(highest(./participation[typeCode="INT" and isNormalParticipation], priorityNumber)/role[classCode="ASSIGNED" and isNormalRole]/player[determinerCode="INST" and classCode=("DEV", "PSN") and isNormalEntity()])
DocumentHeader.section.subject
DefinitionIdentifies the primary subject of the section.
Control0..1
TypeResource(Patient|Group|Device)
Must Understandtrue
RequirementsSubjects can vary, for example mother/baby, patient & relatives, etc.
RIM Mappingunique(./participation[typeCode="SBJ" and isNormalParticipation]/role[typeCode="PAT"]) or unique(./participation[typeCode="SBJ" and isNormalParticipation]/role[typeCode="IDENT"]/player[determinerCode="INST" and classCode=("DEV", "ORG") and isNormalEntity()])
DocumentHeader.section.informant
DefinitionIdentifies the source that recounted the information recorded
Control0..1
TypeResource(Person)
RequirementsProvides context as to the potential accuracy of the information
CommentsGenerally used if information is sourced from a non-clinician (patient, relative, etc.)
RIM Mappingunique(highest(./participation[typeCode="INF" and isNormalParticipation], priorityNumber)/role[classCode="ASSIGNED" and isNormalRole]/player[determinerCode="INST" and classCode=("DEV", "PSN") and isNormalEntity()])
DocumentHeader.section.content
DefinitionIdentifies the discrete data that provides the content for the section.
Control0..1
TypeResource(Any)
Must Understandtrue
RequirementsConveys the discrete data associated with the document.
CommentsBecause documents represent point-in-time snapshots, resource references should generally be to a specific version.
RIM Mappingunique(./outboundRelationship[typeCode="COMP" and isNormalActRelationship()]/target[moodCode="EVN" and classCode!="DOCSECT" and isNormalAct])
To DoThis may need to be 0..*. May need to consider adding text here to to account for missing resources.
DocumentHeader.section.text
DefinitionProvides the text view of the section.
Control0..1
TypeNarrative
CommentsThis will most commonly be used when there is no "content" resource or when the content resource does not provide a "text" element.
RIM Mapping./text[mimeType="text/xhtml"]
DocumentHeader.section.section
DefinitionIdentifies a subtopic within the section as part of the document's table of contents
Control0..*
Type@DocumentHeader.Section
RequirementsAllows more complex document structures
RIM Mapping./outboundRelationship[typeCode="COMP" and isNormalActRelationship()]/target[moodCode="EVN" and classCode="DOCSECT" and isNormalAct]
DocumentHeader.extension
DefinitionSee Extensions
Control0..*
TypeExtension
RIM MappingN/A
DocumentHeader.text
Definition
Control1..1
TypeNarrative
Must Understandtrue
RIM Mapping./text[mimeType="text/plain"]

This is an old version of FHIR retained for archive purposes. Do not use for anything else
Implementers are welcome to experiment with the content defined here, but should note that the contents are subject to change without prior notice.
© HL7.org 2011 - 2012. FHIR v0.05 generated on Sun, Sep 9, 2012 03:28+1000. License