Figure 32: Authenticator example <authenticator> <time value="20050329224411+0500"/> <signatureCode code="S"/> <assignedEntity> <id extension="KP00017" root="2.16.840.1.113883.19"/> <addr> <streetAddressLine>21 North Ave.</streetAddressLine> <city>Burlington</city> <state>MA</state> <postalCode>02368</postalCode> <country>US</country> </addr> <telecom use="WP" value="tel:(555)555-1003"/> <assignedPerson> <name> <given>Henry</given> <family>Seven</family> </name> </assignedPerson> </assignedEntity> </authenticator> relatedDocument A DIR may have three types of parent document: A superseded version that the present document wholly replaces (typeCode = RPLC). DIRs may go through stages of revision prior to being legally authenticated. Such early stages may be drafts from transcription, those created by residents, or other preliminary versions. Policies not covered by this specification may govern requirements for retention of such earlier versions. Except for forensic purposes, the latest version in a chain of revisions represents the complete and current report. An original version that the present document appends (typeCode = APND). When a DIR is legally authenticated, it can be amended by a separate addendum document that references the original. A source document from which the present document is transformed (typeCode = XFRM). A DIR may be created by transformation from a DICOM Structured Report (SR) document or from another DIR. An example of the latter case is the creation of a derived document for inclusion of imaging results in a clinical document. contain zero or one [0..2] such that it MAY relatedDocument When a Diagnostic Imaging Report has been transformed from a DICOM SR document, relatedDocument/@typeCode SHALL be XFRM, and relatedDocument/parentDocument/id SHALL contain the SOP Instance UID of the original DICOM SR document. ().
Figure 32: Authenticator example <authenticator> <time value="20050329224411+0500"/> <signatureCode code="S"/> <assignedEntity> <id extension="KP00017" root="2.16.840.1.113883.19"/> <addr> <streetAddressLine>21 North Ave.</streetAddressLine> <city>Burlington</city> <state>MA</state> <postalCode>02368</postalCode> <country>US</country> </addr> <telecom use="WP" value="tel:(555)555-1003"/> <assignedPerson> <name> <given>Henry</given> <family>Seven</family> </name> </assignedPerson> </assignedEntity> </authenticator> relatedDocument A DIR may have three types of parent document: A superseded version that the present document wholly replaces (typeCode = RPLC). DIRs may go through stages of revision prior to being legally authenticated. Such early stages may be drafts from transcription, those created by residents, or other preliminary versions. Policies not covered by this specification may govern requirements for retention of such earlier versions. Except for forensic purposes, the latest version in a chain of revisions represents the complete and current report. An original version that the present document appends (typeCode = APND). When a DIR is legally authenticated, it can be amended by a separate addendum document that references the original. A source document from which the present document is transformed (typeCode = XFRM). A DIR may be created by transformation from a DICOM Structured Report (SR) document or from another DIR. An example of the latter case is the creation of a derived document for inclusion of imaging results in a clinical document. MAY contain zero or one [0..2] relatedDocument such that it When a Diagnostic Imaging Report has been transformed from a DICOM SR document, relatedDocument/@typeCode SHALL be XFRM, and relatedDocument/parentDocument/id SHALL contain the SOP Instance UID of the original DICOM SR document. ().
sup155.docx