This page is part of the FHIR Specification (v0.06: DSTU 1 Ballot 2). 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 Document - Formal Definitions 2.3.11

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

Document
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
Document.information
DefinitionDefines the medata and context for this document
Control1..1
TypeDocumentInformation
Must Understandtrue
Document.information.id
DefinitionLogical Identifier for the document, assigned when created. This identifier stays constant when subsequent versions of the document are created
Control0..1
TypeIdentifier
Must Understandtrue
Commentssee discussion in resource definition for how these relate
RIM MappingDocument.id / Document.setId
Document.information.versionId
DefinitionVersion specific identifier for the document, assigned when created. This identifier changes when subsequent versions of the document are created
Control0..1
TypeIdentifier
Must Understandtrue
Commentssee discussion in resource definition for how these relate
RIM MappingDocument.id
Document.information.instant
Definitionthe document creation time, when the document first came into being. Where the 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"]
Document.information.class
DefinitionThe code specifying the particular kind of document (e.g., Prescription, Discharge Summary, Report).
Control0..1
TypeCoding
Comments It is suggested that the XDS Affinity Domain draws these values from a coding scheme providing a coarse level of granularity (about 10 to 100 entries). Shall have a single value. This should be an extension
Document.information.type
DefinitionSpecifies 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
Document.information.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
Document.information.confidentialityCode
DefinitionThe code specifying the level of confidentiality of the XDS Document. These codes are specific to an XDS Affinity Domain.
Control1..1
TypeCoding
CommentsEnforcement and issues related to highly sensitive documents are beyond the scope of XDS (see security section). confidentialityCode is part of a codification scheme and value set enforced by the Document Registry.
Document.information.subject
DefinitionIdentifies the primary subject of the document.
Control1..1
TypeResource(Person|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
Document.information.author
DefinitionIdentifies who is responsible for the information in the document. (Not necessarily who typed it in.)
Control1..*
TypeResource(Person|Agent)
RequirementsIdentifies who is responsible for the content.
RIM Mapping./participation[typeCode="AUT" and isNormalParticipation]/role[classCode="ASSIGNED" and isNormalRole()]
Document.information.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]
Document.information.attester.mode
DefinitionThe type of attestation the authenticator offers
Control1..1
Typecode from DocumentAttestationMode
RequirementsIndicates the level of officialness of the attestation.
RIM Mappingunique(./modeCode)
Document.information.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()]
Document.information.attester.party
DefinitionWho attested the document in the specified way
Control0..1
TypeResource(Person|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()]
Document.information.custodian
DefinitionIdentifies the organization or group who is responsible for ongoing maintenance of and access to the document.
Control0..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()]
Document.information.event
DefinitionThe main event/act/item, such as a colonoscopy or an appendectomy, being documented
Control0..1
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])
Document.information.event.code
DefinitionThis list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act.
Control0..*
TypeCodeableConcept
CommentsAn event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more eventCodes are included, they shall not conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as “key words” for certain types of queries.
Document.information.event.period
DefinitionThe period of time covered by the document. There is no assertion that the document is a complete representation for this period, only that it documents events during this time
Control0..1
TypePeriod
Document.information.event.detail
DefinitionFull details for the event(s) the document concents
Control0..*
TypeResource(Any)
Document.information.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])
Document.information.facilityType
DefinitionThis code represents the type of organizational setting of the clinical encounter during which the documented act occurred
Control0..1
TypeCodeableConcept
CommentsIn some cases, the setting of the encounter is inherent in the typeCode, such as "Diabetes Clinic Progress Note". healthcareFacilityTypeCode shall be equivalent to or further specialize the value inherent in the typeCode; for example, where the typeCode is simply "Clinic Progress Note" and the value of healthcareFacilityTypeCode is "private clinic". The value shall not conflict with the value inherent in the typeCode, as such a conflict would create an ambiguous situation
Document.information.practiceSetting
DefinitionThe code specifying the clinical specialty where the act that resulted in the document was performed (e.g., Family Practice, Laboratory, Radiology).
Control0..1
TypeCodeableConcept
CommentsIt is suggested that the XDS Affinity Domain draws these values from a coding scheme providing a coarse level of granularity (about 10 to 100 entries)
Document.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"])
Document.provenance
DefinitionAdditional provenance about the document and the resources that are the sections
Control0..*
TypeResource(Provenance)
Must Understandtrue
Document.stylesheet
DefinitionA fixed stylesheet to use when rendering the documents
Control0..1
TypeAttachment
RIM MappingN/A
Document.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
Document.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]
Document.section.code
DefinitionA code identifying the kind of content contained within the section
Control0..1
TypeCodeableConcept from DocumentSectionCode
RequirementsProvides computable standardized labels to topics within the document.
RIM Mapping./code
Document.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()])
Document.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.
Document.section.section
DefinitionIdentifies a subtopic within the section as part of the document's table of contents
Control0..*
Type@Document.Section
RequirementsAllows more complex document structures
RIM Mapping./outboundRelationship[typeCode="COMP" and isNormalActRelationship()]/target[moodCode="EVN" and classCode="DOCSECT" and isNormalAct]
Document.extension
DefinitionSee Extensions
Control0..*
TypeExtension
RIM MappingN/A
Document.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.06 generated on Tue, Dec 4, 2012 00:04+1100. License