10.07.2015 Views

Centricity PACS Version 1.0 CONFORMANCE STATEMENT for ...

Centricity PACS Version 1.0 CONFORMANCE STATEMENT for ...

Centricity PACS Version 1.0 CONFORMANCE STATEMENT for ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

GEMS INFORMATION TECHNOLOGIESCENTRICITY <strong>PACS</strong> <strong>1.0</strong> <strong>CONFORMANCE</strong> <strong>STATEMENT</strong>REV 0, MAY 2002 IIS FP 106173. Search <strong>for</strong> the SOP Instances records on the Patient / Study / Series / SOP Instance level in the<strong>Centricity</strong> database, as specified in the Retrieve request and using the matching criteria specifiedin the Retrieve request.4. Locate the data files of the found SOP Instances in the <strong>Centricity</strong> storage sub-system. Fetch thedata from the long-term archiving sub-system if necessary.5. If the data files can be located, initiate a separate DICOM association to send these to thedestination AE as specified in the received Retrieve request.2.2.2 Functional Definitions of AE’sThe DICOM Application Entities of <strong>Centricity</strong> <strong>PACS</strong> initiate or receive the DICOM associations tosupport a number of application functions <strong>for</strong> the <strong>PACS</strong> system.2.2.2.1 Storage AEThe Storage AE supports the following application-level functions:xxxReceive SOP instances from a remote DICOM AE.Relate each received instance to an ordered / scheduled study in the <strong>Centricity</strong> <strong>PACS</strong> databaseby matching the Patient / Study in<strong>for</strong>mation in the instance’s data set to the in<strong>for</strong>mation of thedatabase.If no matching can be found, create a new (unordered) study by directly using the Patient / Studyin<strong>for</strong>mation in the received data set and relate the SOP instance to the created study.Note:When relating a SOP Instance to an ordered study, the Storage AE may alter the values ofsome data elements using the values of the counterpart data fields of the matched study in the<strong>Centricity</strong> database. In addition, the SOP Instances may be also changed by the Patient /Study update in<strong>for</strong>mation received from RIS or entered by the <strong>Centricity</strong> Exam Manageroperator. <strong>Centricity</strong> <strong>PACS</strong> does not create a new SOP Instance <strong>for</strong> these data changes. Alater DICOM Query or Retrieve request from remote AE will receive the SOP Instance withsome data elements changed, or may not find the submitted SOP Instance if the changed dataelements are used as the searching keys. A list of the data elements that may undergo datacoercion is given in Section 4.2.3. Data coercion is per<strong>for</strong>med <strong>for</strong> data correction purpose.xxStore the Patient, Study, Series, and SOP Instance relationship permanently in the <strong>Centricity</strong><strong>PACS</strong> database.Store the SOP instances in the <strong>PACS</strong> storage system, <strong>for</strong> use within <strong>Centricity</strong> <strong>PACS</strong> and <strong>for</strong>long-term archiving.Note:<strong>Centricity</strong> <strong>PACS</strong> will properly save and archive all SOP Instances successfully received viathe Storage AE. However, <strong>Centricity</strong> <strong>PACS</strong> cannot guarantee that all received SOPInstances can be properly displayed and printed. Section 4.2.4 lists the detailed applicationlevelfunctions that <strong>Centricity</strong> <strong>PACS</strong> is able to support <strong>for</strong> the successfully received SOPInstances.2–13

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!