Page 444 |
DICOM PS3.17 2020a - Explanatory Information |
|
|
Attribute |
Value |
Comment |
>>Referenced SOP Class UID |
1.2.840.10008.5.1.4.43.1 |
|
>>Referenced SOP Instance UID |
1.2.3.4.5.6.7.0.2 |
|
>>Component ID |
2 |
|
Component Assembly Sequence |
|
|
>Component 1 Referenced ID |
1 |
The stem |
>Component 1 Referenced Mating Feature Set ID |
1 |
|
> Component 1 |
Referenced Mating Feature ID |
1 |
|
>Component 2 Referenced ID |
2 |
The cup |
> Component 2 |
Referenced Mating Feature Set ID |
1 |
|
> Component 2 |
Referenced Mating Feature ID |
1 |
|
ZZ.5 Implant Template Versions and Derivation
The Generic Implant Module contains several Attributes to express the relations between different versions of implant templates. These Attributes are
(0022,1097) |
Implant Part Number |
Number (or alphanumerical code) assigned by the manufacturer of an implant |
|
|
to one particular release of one particular part. Whenever changes on the |
|
|
implant design are made, a new implant part number is assigned. |
(0068,6226) |
Effective DateTime |
Date and time from which on an Implant Template Instance is valid. |
(0068,6221) |
Implant Template Version |
Number assigned by the creator of an ORIGINAL Implant Template Instance. |
|
|
When an implant manufacturer issues a new version of an implant template |
|
|
without doing changes on the implant itself, it issues a new instance with the |
|
|
same part number but a different template version. |
(0068,6222) |
Replaced Implant Template |
WhenamanufacturerissuesanewversionofanImplantTemplate,theinstance |
|
Sequence |
contains a reference to it direct predecessor. |
(0068,6223) |
Implant Type |
When a software vendor, user or other entity creates a "proprietary" version |
|
|
of an Implant Template by adding Attributes, the resulting Instance is labeled |
|
|
DERIVED. |
(0068,6225) |
Original Implant Template |
When an Instance is DERIVED, it contains a reference to the ORIGINAL |
|
|
instance it was derived from (directly or with several derived versions in |
|
|
between). |
(0068,6224) |
Derivation Implant Template WhenanImplantTemplateInstanceisderivedfromanotherinstance,itcontains |
|
Sequence |
a reference to the Implant Template Instance it was directly derived from. |
Different versions of Implant Templates reflect the changes a manufacturer is doing on the Implant Templates he issues. The Implant Templates that are issued by a manufacturer (or a third party who is acting on behalf of the manufacturer) are always ORIGINAL. Softwarevendors,PACSintegrators,orotherstakeholderswilladdinformationtosuchtemplatesfordifferentpurposes.TheInstances that are generated by this process is called derivation and the resulting instances are labeled DERIVED. Implantation Plans, i.e., electronicdocumentsdescribingtheresultofimplantationplanning,arespecifiedinaninstanceoftheImplantationPlanSRDocument. There, the implants that are relevant for one plan are included by reference. When such plans are exchanged between systems or organizationsitislikelythatthereceivingpartyhasaccesstootherversionsoftemplatesasthesendingpartyhas.Inordertomaintain readability of exchanged plans, the following is required:
•All necessary information about an implant that is relevant to display and understand a plan is present in the ORIGINAL Implant Templates that were issued by a manufacturer. This is assured by these Attributes being Type 1 in the IOD.
•When deriving Instances, information may only be added but not removed from the ORIGINAL Instance. This information may be encoded in standard or private Tags.
•Derived Instances contain the information about the source Instances they were derived from. All Instances contain a reference to the ORIGINAL Instance they were derived from. If an application receives a plan that references an implant it does not have in its