Template

Show index

Template BC Attachment 2017‑03‑30 04:17:59

Id2.16.840.1.113883.3.1818.10.4.1Effective Date2017‑03‑30 04:17:59
Statusdraft DraftVersion Label
NameBCAttachmentDisplay NameBC Attachment
Description

The Attachments template is used to reference any external file within the context of a part of the patient’s record (e.g. lab results, x-ray images, etc.). There are many use cases where clinical content may not be incorporated discretely into the EMR system, but linked to the relevant record through the attachment mechanism.

When an external file is attached to the patient’s medical record there are certain meta data regarding that file that must be captured and communicated with the file to ensure that the context of the external file in relation to the medical record is maintained. This meta data may include the date the attachment is received, its title and author. The addition of keywords may also be used to facilitate searching, filtering and sorting attachments within the EMR. Additionally, the EMR may provide the ability for the user to add notes or observations regarding the attachment for future reference.

The Attachment itself may be embedded into the CDA document; or, more commonly referenced as an external document located within the message wrapper, a recognized file system, or at a web location. Refer to the EncapsulatedDatatemplate for details on the transmission of attached files. 

ContextParent nodes of template element with id 2.16.840.1.113883.3.1818.10.4.1
ClassificationCDA Entry Level Template
Open/ClosedOpen (other than defined elements are allowed)
Used by / Uses
Used by 0 transactions and 8 templates, Uses 3 templates
Used by as NameVersion
2.16.840.1.113883.3.1818.10.3.1Containmentdraft BC Advance Directives Observation2017‑04‑02 05:27:12
2.16.840.1.113883.3.1818.10.3.2Containmentdraft BC Alert Observation2017‑04‑02 05:53:46
2.16.840.1.113883.3.1818.10.3.9Containmentdraft BC Encounter Event2017‑04‑02 22:14:30
2.16.840.1.113883.3.1818.10.3.13Containmentdraft BC Medical Imaging Observation2017‑04‑03 02:39:51
2.16.840.1.113883.3.1818.10.3.14Containmentdraft BC Order Event2017‑04‑03 03:39:13
2.16.840.1.113883.3.1818.10.3.19Containmentdraft BC Unclassified Documents Organizer2017‑04‑03 05:37:49
2.16.840.1.113883.3.1818.10.4.18Containmentdraft BC Outcome Observation2017‑04‑01 07:16:29
2.16.840.1.113883.3.1818.10.4.25Containmentdraft BC Result Component Observation2017‑04‑02 02:07:20
Uses as NameVersion
2.16.840.1.113883.3.1818.10.4.3Containmentdraft BC Comment ObservationDYNAMIC
2.16.840.1.113883.3.1937.777.17.10.4Containmentdraft BC Date ObservationDYNAMIC
2.16.840.1.113883.3.1937.777.17.10.5Containmentdraft BC Encapsulated DataDYNAMIC
RelationshipSpecialization: template 2.16.840.1.113883.10.12.303 CDA Observation (2005‑09‑07)
ref
ad1bbr-
ItemDTCardConfDescriptionLabel
hl7:observation
1 … 1MCONF‑1205
@classCode
cs1 … 1FOBSCONF‑1206
@moodCode
cs1 … 1FEVNCONF‑1207
hl7:templateId
II1 … 1MCONF‑1205
@root
uid1 … 1F2.16.840.1.113883.3.1818.10.4.1
hl7:templateId
II1 … 1RCONF‑1205
@root
uid1 … 1F2.16.840.1.113883.10.12.303
hl7:id
II1 … 1MCONF‑1208
hl7:code
CD (required)1 … 1MCONF‑1209
@code
CONF1 … 1FATTACH
@codeSystem
1 … 1F2.16.840.1.113883.3.3068.10.6.3
@displayName
1 … 1FAttachment
@codeSystemName
1 … 1FObservationType-CA-Pending
hl7:text
ED0 … 1CONF‑1212
hl7:effectiveTime
IVL_TS1 … 1RCONF‑1210
hl7:value
CD1 … 1RCONF‑1211
 CONF
The value of @code shall be drawn from value set 2.16.840.1.113883.3.3068.10.8.14 AttachmentObservationType (DYNAMIC)
hl7:entryRelationship
0 … *Contains 2.16.840.1.113883.3.1818.10.4.3 BC Comment Observation (DYNAMIC)CONF‑1213
hl7:entryRelationship
0 … 1RContains 2.16.840.1.113883.3.1937.777.17.10.4 BC Date Observation (DYNAMIC)CONF‑1214
hl7:entryRelationship
0 … *RContains 2.16.840.1.113883.3.1937.777.17.10.5 BC Encapsulated Data (DYNAMIC)CONF‑1215