Id |
2.16.840.1.113883.10.20.22.2.86 |
Effective Date |
2019‑03‑06 11:52:10
|
Status |
Draft
|
Version Label |
2.1 |
Name |
ProductInstance |
Display Name |
Product Instance |
Description |
This clinical statement represents a particular device that was placed in a patient
or used as part of a procedure or other act. This provides a record of the identifier
and other details about the given product that was used. For example, it is important
to have a record that indicates not just that a hip prostheses was placed in a patient
but that it was a
particular hip prostheses number with a unique identifier. The FDA Amendments Act
specifies the creation of a Unique Device Identification (UDI) System that requires
the label of devices to bear a unique identifier that will standardize device identification
and identify the device through distribution and use. The FDA permits an issuing agency
to designate that their Device
Identifier (DI) + Production Identifier (PI) format qualifies as a UDI through a process
of accreditation. Currently, there are three FDA-accredited issuing agencies that
are allowed to call their format a UDI. These organizations are GS1, HIBCC, and ICCBBA.
For additional information on technical formats that qualify as UDI from each of the
issuing agencies see the UDI Appendix.
When communicating only the issuing agency device identifier (i.e., subcomponent of
the UDI), the use of the issuing agency OID is appropriate. However, when communicating
the unique device identifier (DI + PI), the FDA OID (2.16.840.1.113883.3.3719) must
be used. When sending a UDI, populate the participantRole/id/@root with the FDA OID
(2.16.840.1.113883.3.3719) and
participantRole/id/@extension with the UDI. When sending a DI, populate the participantRole/id/@root
with the appropriate assigning agency OID and participantRole/id/@extension with the
DI. The scopingEntity/id should correspond to FDA or the appropriate issuing agency.
|
|
Context |
Parent nodes of template element with id 2.16.840.1.113883.10.20.22.2.86 |
Classification |
CDA Entry Level Template |
Open/Closed |
Open (other than defined elements are allowed) |
Used by / Uses |
Used by 0 transactions and 4 templates, Uses 0 templates |
|
|
Relationship |
Specialization: template 2.16.840.1.113883.10.20.22.2.86 (2015‑08‑13)
ref
?
Specialization: template 2.16.840.1.113883.10.12.321 CDA Participant (Body) (2005‑09‑07)
ref
ad1bbr-
|
Item |
DT |
Card |
Conf |
Description |
Label |
|
|
|
|
|
(Pro nce) |
 |
@classCode
|
|
cs |
1 … 1 |
F |
MANU |
CONF 7900 |
|
SHALL contain exactly one [1..1] @classCode="MANU" Manufactured Product (CodeSystem:
RoleClass urn:oid:2.16.840.1.113883.5.110 STATIC) (CONF:81-7900).
|
 |
hl7:templateId
|
|
II |
1 … 1 |
M |
|
(Pro nce) |
 |
 |
@root
|
|
uid |
1 … 1 |
F |
2.16.840.1.113883.10.20.22.2.86 |
 |
cda:templateId
|
|
II |
1 … 1 |
M |
SHALL contain exactly one [1..1] templateId (CONF:81-7901) such that it |
CONF 7901 |
 |
 |
@root
|
|
uid |
1 … 1 |
F |
2.16.840.1.113883.10.20.22.2.86 |
CONF 0522 |
|
SHALL contain exactly one [1..1] @root="2.16.840.1.113883.10.20.22.4.37" (CONF:81-10522). |
 |
cda:id
|
|
II |
1 … * |
|
SHALL contain at least one [1..*] id (CONF:81-7902). |
CONF 7902 |
 |
cda:playingDevice
|
|
|
1 … 1 |
M |
SHALL contain exactly one [1..1] playingDevice (CONF:81-7903). |
CONF 7903 |
 |
 |
cda:code
|
|
|
0 … 1 |
R |
This playingDevice SHOULD contain zero or one [0..1] code (CONF:81-16837). |
CONF 6837 |
 |
cda:scopingEntity
|
|
|
1 … 1 |
M |
SHALL contain exactly one [1..1] scopingEntity (CONF:81-7905). |
CONF 7905 |
 |
 |
cda:id
|
|
II |
1 … * |
|
This scopingEntity SHALL contain at least one [1..*] id (CONF:81-7908). |
CONF 7908 |
|