000107 - Agfa HealthCare
000107 - Agfa HealthCare 000107 - Agfa HealthCare
Page 18 of 25MED/RLR/000107Document No. 000107, Revision 3.111 September, 2000 Agfa Medical ImagingImpax requests the following elements for this SOP class:Module Attribute Name Tag MatchSOP Common Specific Character Set (0008,0005)Scheduled Procedure Step Scheduled Procedure Step Sequence (0040,0100)> Scheduled Station AE Title (0040,0001)> Scheduled Procedure Step Start Date (0040,0002)> Scheduled Procedure Step Start Time (0040,0003)> Modality (0008,0060)> Scheduled Procedure Step Desc. (0040,0005)> Scheduled Station Name (0040,0010)> Scheduled Procedure Step Location (0040,0011)Requested Procedure Requested Procedure ID (0040,1001)Requested Procedure Description (0032,1060)Reason for Requested Procedure (0040,1002)Requested Procedure Code Sequence (0032,1064)> Code Value (0008,0100)Study Instance UID (0020,000D) SVImaging Service Request Accession Number (0008,0050) SVRequesting Physician’s Name (0032,1032)Referring Physician’s Name (0008,0090)Reason for Imaging Service Request (0040,2001)Visit Status Current Patient Location (0038,0030)Visit RelationshipReferenced Patient Sequence (0008,1120)> Referenced SOP Class UID (0008,1150)> Referenced SOP Instance UID (0008,1155)Patient Identification Patient Name (0010,0010)Patient ID (0010,0020) SVPatient Demographic Patient Birth Date (0010,0030)Patient Sex (0010,0040)Table 3.18 Modality Worklist information model attributes.3.1.3 Association Acceptance Policy3.1.3.1 Real World Activity - Verification3.1.3.1.1 Associated Real World Activity - VerificationImpax will respond to Verification requests to provide an SCU with the ability to determine if Impax isreceiving DICOM requests.3.1.3.1.2 Presentation Context Table - VerificationImpax will accept any of the Presentation Contexts listed in Table 3.19 for Verification.Abstract SyntaxSOP Class SOP Class UIDTransfer Syntax Role Extended NegotiationVerification 1.2.840.10008.1.1 All from Table 3.3 SCU NoneTable 3.19 Presentation contexts.A]
MED/RLR/000107 Page 19 of 25Document No. 000107, Revision 3.1Agfa Medical Imaging 11 September, 20003.1.3.1.3 SOP Specific Conformance - VerificationImpax provides standard conformance to the DICOM Verification Service Class. Impax returns one of thefollowing status codes:Service Status Further Meaning Protocol Codes Related Fields DescriptionSuccess Success 0000 - Operation performed properlyTable 3.20 Verification status codes.3.1.3.1.4 Presentation Context Acceptance Criterion - VerificationImpax will always accept a Presentation Context for the Verification SOP Class with the default DICOMtransfer syntax listed in Table 3.3.3.1.3.1.5 Transfer Syntax Selection Policies - VerificationSince no DICOM data object is associated with a Verification command, only the default DICOM transfersyntax is required/supported.3.1.3.2 Real World Activity - Detached Patient Management3.1.3.2.1 Associated Real World Activity - Detached Patient ManagementImpax will accept N-EVENT-REPORTs to indicate that a change in the status of patient information hasoccurred. The following events are supported:Patient Updated3.1.3.2.2 Presentation Context Table - Detached Patient ManagementImpax supports the presentation contexts listed in Table 3.21.Abstract SyntaxSOP ClassSOP Class UIDTransfer Syntax Role Extended NegotiationDetached Patient Management 1.2.840.10008.3.1.2.1.1 All from Table 3.3 SCU NoneTable 3.21 Presentation contexts.A]
- Page 2 and 3: Page 2 of 25MED/RLR/000107Document
- Page 5 and 6: MED/RLR/000107 Page 5 of 25Document
- Page 7 and 8: MED/RLR/000107 Page 7 of 25Document
- Page 9 and 10: MED/RLR/000107 Page 9 of 25Document
- Page 11 and 12: MED/RLR/000107 Page 11 of 25Documen
- Page 13 and 14: MED/RLR/000107 Page 13 of 25Documen
- Page 15 and 16: MED/RLR/000107 Page 15 of 25Documen
- Page 17: MED/RLR/000107 Page 17 of 25Documen
- Page 21 and 22: MED/RLR/000107 Page 21 of 25Documen
- Page 23 and 24: MED/RLR/000107 Page 23 of 25Documen
- Page 25: MED/RLR/000107 Page 25 of 25Documen
Page 18 of 25MED/RLR/<strong>000107</strong>Document No. <strong>000107</strong>, Revision 3.111 September, 2000 <strong>Agfa</strong> Medical ImagingImpax requests the following elements for this SOP class:Module Attribute Name Tag MatchSOP Common Specific Character Set (0008,0005)Scheduled Procedure Step Scheduled Procedure Step Sequence (0040,0100)> Scheduled Station AE Title (0040,0001)> Scheduled Procedure Step Start Date (0040,0002)> Scheduled Procedure Step Start Time (0040,0003)> Modality (0008,0060)> Scheduled Procedure Step Desc. (0040,0005)> Scheduled Station Name (0040,0010)> Scheduled Procedure Step Location (0040,0011)Requested Procedure Requested Procedure ID (0040,1001)Requested Procedure Description (0032,1060)Reason for Requested Procedure (0040,1002)Requested Procedure Code Sequence (0032,1064)> Code Value (0008,0100)Study Instance UID (0020,000D) SVImaging Service Request Accession Number (0008,0050) SVRequesting Physician’s Name (0032,1032)Referring Physician’s Name (0008,0090)Reason for Imaging Service Request (0040,2001)Visit Status Current Patient Location (0038,0030)Visit RelationshipReferenced Patient Sequence (0008,1120)> Referenced SOP Class UID (0008,1150)> Referenced SOP Instance UID (0008,1155)Patient Identification Patient Name (0010,0010)Patient ID (0010,0020) SVPatient Demographic Patient Birth Date (0010,0030)Patient Sex (0010,0040)Table 3.18 Modality Worklist information model attributes.3.1.3 Association Acceptance Policy3.1.3.1 Real World Activity - Verification3.1.3.1.1 Associated Real World Activity - VerificationImpax will respond to Verification requests to provide an SCU with the ability to determine if Impax isreceiving DICOM requests.3.1.3.1.2 Presentation Context Table - VerificationImpax will accept any of the Presentation Contexts listed in Table 3.19 for Verification.Abstract SyntaxSOP Class SOP Class UIDTransfer Syntax Role Extended NegotiationVerification 1.2.840.10008.1.1 All from Table 3.3 SCU NoneTable 3.19 Presentation contexts.A]
Change language