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 Sequence |
When a manufacturer issues a new version of an Implant Template, the instance 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 Sequence |
When an Implant Template Instance is derived from another instance, it contains 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. Software vendors, PACS integrators, or other stakeholders will add information to such templates for different purposes. The Instances that are generated by this process is called derivation and the resulting instances are labeled DERIVED. Implantation Plans, i.e., electronic documents describing the result of implantation planning, are specified in an instance of the Implantation Plan SR Document. There, the implants that are relevant for one plan are included by reference. When such plans are exchanged between systems or organizations it is likely that the receiving party has access to other versions of templates as the sending party has. In order to maintain 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 database, it will find the UID of the ORIGINAL Instance in the plan, too. It can query its database for an instance that was derived from that Instance and thereby find an Instance it can use to present the plan.
Figure ZZ.5-1 shows an example of the relationships between two versions of a manufacturer's Implant Template and several different Implant Templates derived by software vendors from these versions.
