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 XdsEntry2 - Formal Definitions 3.19.6

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

XdsEntry2
DefinitionAn entry in an XDS registry
Control1..1
XdsEntry2.id
DefinitionDocument identifier as assigned by the source of the document. This identifier is version specific. This unique identifier may be used in the body of other Documents etc to reference this document.
Control1..1
TypeIdentifier
CommentsThe length of the id shall not exceed 128 bytes. The structure and format of this Id shall be consistent with the specification corresponding to the format attribute. (e.g., for a DICOM standard document a 64 character numeric UID - urn:oid:, for an HL7 CDA format a serialization of the CDA Document id extension and root in the form oid^extension - hl7-att:, where OID is a 64 digits max, and the ID is a 16 UTF-8 char max). If the oid is coded without the extension then the '^' character shall not be included. This uniqueId is intended to provide the means to reference this XDS document from within the content of another document. Neither the XDS Registry nor the Repository is aware of such references, but the Document Sources and Consumers are
XdsEntry2.information
DefinitionDocument metadata that is used for searching for the document
Control0..1
TypeDocumentInformation
CommentsThe document metadata reflects what is in the document itself and is never updated once the entry is created
XdsEntry2.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
XdsEntry2.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
XdsEntry2.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"]
XdsEntry2.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
XdsEntry2.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
XdsEntry2.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
XdsEntry2.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.
XdsEntry2.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
XdsEntry2.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()]
XdsEntry2.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]
XdsEntry2.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)
XdsEntry2.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()]
XdsEntry2.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()]
XdsEntry2.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()]
XdsEntry2.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])
XdsEntry2.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.
XdsEntry2.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
XdsEntry2.information.event.detail
DefinitionFull details for the event(s) the document concents
Control0..*
TypeResource(Any)
XdsEntry2.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])
XdsEntry2.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
XdsEntry2.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)
XdsEntry2.format
DefinitionCode globally uniquely specifying the format of the document. Along with the information.type, it should provide sufficient information to allow any potential Document Consumer to know if it will be able to process the document. The formatCode shall be sufficiently specific to ensure processing/display by identifying a document encoding, structure and template (e.g., for a CDA Document, the fact that it complies with a CDA schema, possibly a template and the choice of a content-specific style sheet).
Control1..1
TypeCoding
CommentsFormat codes may be specified by multiple organizations. Format codes defined by ITI shall have names with the prefix urn:ihe:iti:. Format codes defined by other IHE domains shall have names with the prefix urn:ihe:’domain initials’: Format codes defined by the Affinity Domain shall have names with the prefix urn:ad:’name of affinity domain’: Affinity Domains shall be unique. The prefixes described here are not assumed to be exhaustive.
XdsEntry2.availability
Definitiondeprecated documents can be included in some responses
Control1..1
Typecode from XdsEntryAvailability
CommentsThis attribute is always set to Approved as part of the submission of new XDS Documents. It may be changed to Deprecated under the primary responsibility of the Document Source with possible patient supervision. Although XDS supports the ability to delete documents, there is no such state as “the Document Entry is removed” (only an audit trail is kept if such a deletion is allowed).
XdsEntry2.folder
DefinitionFolders that this document is registered in
Control0..*
TypeResource(XdsFolder)
XdsEntry2.subject
DefinitionThe subject of care information that the document is about. This is different from the documentInformation.subject because that never changes from what the document says. This value may be updated if the subject details are updated (e.g. merged) and will then differ from the original document
Control0..1
TypeResource(Person|Patient|Group|Device)
CommentsThe system is the "Authority Domain Id" (enforced by the Registry), and the identifier is an Id in the above domain. This subject is intended to be updated after the Document is registered (where as the Document content and Document.information.subject itself will not be updated without changing the whole document).
XdsEntry2.content
DefinitionReference to the content, along with additional information such as size, hash, language etc
Control0..1
TypeAttachment
XdsEntry2.extension
DefinitionSee Extensions
Control0..*
TypeExtension
RIM Mapping[varies]
XdsEntry2.text
DefinitionText summary of resource (for human interpretation)
Control1..1
TypeNarrative

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