Home > Philips > Ultrasound System > Philips Hd9 Owners Manual

Philips Hd9 Owners Manual

    Download as PDF Print this page Share this page

    Have a look at the manual Philips Hd9 Owners Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 619 Philips manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    							4 NETWORKING 
    4.1  IMPLEMENTATION MODEL 
    4.1.1  Application Data Flow 
    Acquire 
    Images /  Reports
    Storage 
    Application  Entity
    Workflow 
    Application  Entity
    Hardcopy 
    Application  Entity
    Remote 
    Application Entity 
    Receives Images  & Reports
    Search 
    Worklist
    Acquire  Images
    Remote 
    Application Entity 
    Provides Worklist  Items
    Remote 
    Application Entity  Receives MPPS  Create/Update
    Remote 
    Application Entity  Confirms  
    CommitmentsRequest 
    Commitments
    Acquire  ImagesRemote 
    Application Entity 
    Prints Film Sheets
    DICOM Standard Interface
     
    Figure 4.1-1   
    APPLICATION DATA FLOW DIAGRAM 
    HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 11   
       
    -  The Storage Application Entity sends images, Stru
    ctured Reports and requests Storage Commitment to a 
    remote AE. It is associated with the local real-world  activities “Acquire” for Send As You Go, “End Exam” for 
    “Batch”, “DICOM Send” for Manual or “SEND” fr om Exam Directory. Commitment requests are made  
    						
    							HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 12   
       
    automatically.    Methods to send images depend on user configuration, “Batch”, “Send 
    As You Go” or “Manual”.   
    “Manual” mode is performed upon user request for each  study or for specific images selected.    “Batch” mode 
    starts to send images at End Exam for each study.    “Send As You Go” mode starts when the first image is 
    acquired for each study and images are tr ansferred immediately after acquisition.     
    Structured Reports are sent at End Exam for each st udy, or from Exam Directory, selecting “SEND”. 
    If the remote AE is configured as an archive device,  the Storage AE will request Storage Commitment and if a 
    commitment is successfully obtained, it will record this in formation in the local database and displayed it in the 
    Exam List. 
    -  The Workflow Application Entity re ceives Worklist information from and sends MPPS information to a remote 
    AE. It is associated with the local real-world activities  “Search” and “Acquire Images”. When the “Search” local 
    real-world activity is performed, the Workflow App lication Entity queries a remote AE for worklist items and 
    provides the set of worklist items matching the query r equest. “Search” is performed as a result of an operator 
    request, at system Startup, or can be performed automatic ally at specific time intervals.  When the “Acquire 
    Images” local real-world activity is performed, the Workflow Application Entity creates and updates Modality 
    Performed Procedure Step instances managed by a remote  AE. Acquisition of images will result in automated 
    creation of an MPPS Instance. Completion of the M PPS is performed at End Exam for each study.    No 
    Cancel is available. 
    -  The Hardcopy Application Entity prints images on a remo te AE (Printer). It is associated with the local real-
    world activity “Acquire” when a DICOM printer is configur ed, “Print” from the Exam Directory or “DICOM Print” 
    from Image review.    Methods to film images depend on us er configuration and are equal to the actions of 
    sending images of the Storage Application Entity.   
    4.1.2  Functional Definition of AE’s 
    4.1.2.1  Functional Definition of Storage Application Entity 
    The existence of a send job with associated network destinati on will activate the Storage AE. An association request is 
    sent to the destination AEs and upon successful negotiation of  a Presentation Context, the image transfer is started. If 
    the association cannot be opened, the re lated send job is set to an error state and can be restarted by the user via 
    DICOM manager interface or automatically. An automatic retr y (retry interval, retry count) can be configured using the 
    Setup/DICOM Menu. 
    4.1.2.2  Functional Definition of Workflow Application Entity 
    Worklist Search attempts to download a Worklist from a remote node. If the Workflow AE establishes an association to 
    a remote AE, it will transfer all matching worklist items via the open Association.    By default, Worklist Update use “US” 
    for Modality, current date for Scheduled Procedure Step Start Date and blank for Scheduled Station AE Title as query 
    parameters.    The results will be displayed in a separate list, which will be cl eared with the next Worklist Seach. 
    Additional search parameters include: 
    •  On Statup and Every x minutes, with x allowed to be 1 – 60, default of 5 
    •  Scheduled Station AE Title 
    o Any 
    o  This Station 
    o  Another 
    •   Scheduled Procedure Step Start Date 
    o Today (default) 
    o   Range (Prior 0 (default); Next 0 (default) with Prior and Next range of 1-60 days 
    o  Past Week  
    						
    							HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 13   
       
    o
     Past Month 
    o   Custom (specific Date, single value matching) 
    The Workflow AE performs the creation of an MPPS Instance automatically whenever the  first image is acquired for 
    each study.    The MPPS final states can only be set by “End Exam” for each study. 
    4.1.2.3  Functional Definition of Hardcopy Application Entity 
    The existence of a print job will activate the Hardcopy AE.    An association is established with the printers and the 
    printer’s status determined.    If the printer is operating normally, the film sheets described within the print job will be 
    printed.    If the printer is not operating normally, the print j ob will set to an error state and can be restarted by the user 
    via DICOM manager interface or automatically.    An automatic  retry (retry interval, retry count) can be configured using 
    the Setup/DICOM Menu. 
     
      
    						
    							4.1.3 Sequencing of Real-World Activities 
     
    Figure 4.1-2 
    SEQUENCING CONTRAINTS – SEND AS YOU GO 
    HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 14   
        
    						
    							StorageHardcopyWorkflowDepartment SchedulerPrinterImage Manager
    1. Query Worklist
    2. Receive Worklist
    3. Select Workitem
    5. Start Acquisition (Create MPPS)
    9. Store Acquired Images
    8. Print Acquired Images
    10. Complete Acquisition (Finalize MPPS)
    6. Acquire Image
    12. Commit Acquired Images & SR Documents
    13. Receive Commitment Result
    7. End Exam
    11. Store SR Documents
    4. Start Exam
     
    Figure 4.1-3 
    SEQUENCING CONSTRAINTS – BATCH MODE 
     
    Under normal scheduled workflow conditions, the sequencing constraints are illustrated in  Figure 4.1-2 and Figure 
    4.1-3 . 
    Other workflow situations (e .g. unscheduled procedure steps) will have ot her sequencing constraints. Printing could 
    equally take place after the images acquired have been stored.  Printing could be omitted completely if no printer is 
    connected or hardcopies are not required. 
    HD9 1.1.x DICOM Conformance Statement
     989605375630044 Rev. B Page 15   
        
    						
    							HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 16   
       
    4.2 
    AE SPECIFICATIONS   
    4.2.1  Storage Application Entity Specification 
    4.2.1.1  SOP Classes 
    HD9 provides Standard Conformance  to the following SOP Classes: 
    Table 4.2-1 
    SOP CLASSES FOR AE STORAGE 
    SOP Classes  SOP Class UID SCU SCP 
    Ultrasound Image Storage  1.2.840.10008.5.1.4.1.1.6.1 Yes  No 
    Ultrasound Multi-frame Image Storage  1.2.840.10008.5.1.4.1.1.3.1 Yes No 
    Comprehensive Structured Report Storage 1.2.840.10008.5.1.4.1.1.88.33 Yes No 
    Storage Commitment Push Model  1.2.840.10008.1.20.1  Yes No 
    Verification 1.2.840.10008.1.1  Yes Yes 
     
     
    4.2.1.2  Association Policies 
    4.2.1.2.1  General 
    The DICOM Standard application context name for DICOM 3.0 is always proposed: 
    Table 4.2-2 
    DICOM APPLICATION CONTEXT FOR AE STORAGE 
    Application Context Name  1.2.840.10008.3.1.1.1 
     
    4.2.1.2.2  Number of Associations 
    HD9 can initiate one or more Associations at a time for eac h destination to which a transfer request is being processed 
    in the active job queue list.   
    Table 4.2-3 
    NUMBER OF ASSOCIATIONS INITIATED FOR AE STORAGE 
    Maximum number of simultaneous Associations  Unlimited 
     
    HD9 accepts Associations to receive N-EVENT-REPORT notificati ons for the Storage Commitment Push Model SOP 
    Class. 
    Table 4.2-4 
    NUMBER OF ASSOCIATIONS ACCEPTED FOR AE STORAGE 
    Maximum number of simultaneous Associations  Unlimited 
    4.2.1.2.3 Asynchronous Nature 
    HD9 does not support asynchronous communications (multipl e outstanding transactions over a single Association). 
    Table 4.2-5 
    ASYNCHRONOUS NATURE AS A SCU FOR AE STORAGE 
    Maximum number of outstanding asynchronous transactions  1  
    						
    							HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 17   
       
    4.2.1.2.4 
    Implementation Identifying Information 
    The implementation information for this Application Entity is: 
    Table 4.2-6 
    DICOM IMPLEMENTATION CLASS AND VERSION FOR AE STORAGE 
    Implementation Class UID  1.3.46.670589.14.2 
    Implementation Version Name  HD9 1.1 
     
    4.2.1.3 Association Initiation Policy 
    4.2.1.3.1  Activity – Send Images and Structured Reports and Request 
    Commitment 
    4.2.1.3.1.1  Description and Sequencing of Activities 
    A user can select exams or images and request them to be se nt to some destination.    Each request is forwarded to 
    the job queue and processed individually.    When the “Batch ” or “Send As You Go” option is active, Stored images and 
    reports will be forwarded to the network job queue for a pre- configured auto-send target destination automatically.    For 
    “Batch” and “Manual” configuratio n, the system opens an association, send s all images in the study, and closes the 
    association.    If “Send As You Go” is se lected, the system handles the associat ion with the Storage SCP Server using 
    the following method. 
    a.  Open an Association when the first image is acquir ed, and keep association open until the study is closed. 
    b.  If an error occurs while sending an image to the server because there is no longer an open association  (server timed-out), attempt to re-establish the association. 
    c.  When the study is closed, the  open association closes after images  remaining in that study are sent. 
    Structured Reports are only sent over a separate association at End Exam. 
    If the remote AE is configured as an archive device, the  Storage AE will, after all images and reports have been sent, 
    transmit Storage Commitment request (N-ACTION) over a sepa rate Association. The Storage AE can only receive an 
    N-EVENT-REPORT request in  a subsequent association initiated by the SCP.  
    						
    							Storage AEImage Manager
    1. Open Association
    2. C-STORE (Images)
    3. Close Association
    4. Open Association
    5. C-STORE (SR Documents)
    6. Close Association
    7. Open Association
    8. N-ACTION (Storage Commitment Request for Images & SR Documents)
    9. Close Association
    10. Open Association
    11. N-EVENT-REPORT (Storage Commitment Response)
    12. Close Association
     
    Figure 4.2-1 
    SEQUENCING OF ACTIVITY - SEND IMAGES 
    A possible sequence of interactions between the Storage  AE and an Image Manager (e.g. a storage or archive device 
    supporting the Storage and Storage Commitment SOP Classe s as an SCP) is illustrated in the figure above. 
    NOTE: The N-EVENT-REPORT must be sent over a separate association initiated by the Image Manager. (See 
    Section  4.2.1.4) 
     
    HD9 1.1.x DICOM Conformance Statement
     989605375630044 Rev. B Page 18   
        
    						
    							HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 19   
       
    4.2.1.3.1.2 
    Proposed Presentation Contexts 
    HD9 is capable of proposing the Presentation Contexts shown in the following table. 
    Table 4.2-7 
    PROPOSED PRESENTATION CONTEXTS FOR ACTIVITY SEND IMAGES 
    Presentation Context Table 
    Abstract Syntax  Transfer Syntax Role Ext. 
    Neg. 
    Name  UID Name List  UID List 
    Ultrasound Image 
    Storage  1.2.840.10008.5.
    1.4.1.1.6.1 Implicit VR Little Endian 
    JPEG Lossy Baseline  1.2.840.10008.1.2 
    1.2.840.10008.1.2.4.50 
    SCU None 
    Ultrasound Multi-
    frame Image Storage 1.2.840.10008.5.
    1.4.1.1.3.1 
    JPEG Lossy Baseline 
    1.2.840.10008.1.2.4.50 SCU None 
    Comprehensive 
    Structured Report 
    Storage  1.2.840.10008.5.
    1.4.1.1.88.33 
    Implicit VR Little Endian 
    1.2.840.10008.1.2 SCU None 
    Storage Commitment 
    Push Model  1.2.840.10008.1.
    20.1 Explicit VR Little Endian 
    Implicit VR Little Endian 
    Explicit VR Big Endian    1.2.840.10008.1.2.1 
    1.2.840.10008.1.2 
    1.2.840.10008.1.2.2 
    SCU None 
    Verification  
    1.2.840.10008.1.
    1 Explicit VR Little Endian 
    Implicit VR Little Endian 
    Explicit VR Big Endian    1.2.840.10008.1.2.1 
    1.2.840.10008.1.2 
    1.2.840.10008.1.2.2 
    SCU None 
    Presentation Contexts for Ultrasound Image Storage and Ul
    trasound Multi-frame Image Storage will be proposed for 
    the “Storage” device configured in Setup/DICOM. 
    A Presentation Context for Comprehensive Structured Report Storage will be  proposed for the “Storage SR” device 
    configured in Setup/DICOM. 
    A Presentation Context for Storage Commitment Push Model  will be proposed for the “SC” device configured in 
    Setup/DICOM. 
    A Presentation Context for Verification will be proposed when  a user presses the “Test” button for a configured device. 
    4.2.1.3.1.3 SOP Specific Conformance Image & Comprehensive Structured Report Storage SOP 
    Classes 
    All Image and Structured Report Storage SOP Classes support ed by the Storage AE exhibit the same behavior, except 
    where stated, and are described together in this section. 
    Table 4.2-8 
    STORAGE C-STORE RESPONSE STATUS HANDLING BEHAVIOR 
    Service Status  Further Meaning  Error Code  Behavior 
    Success Success  0000 The SCP has successfully stored the SOP Instance. If 
    all SOP Instances succeed, the job is marked as 
    complete. 
    Refused 
    Out of Resources  A700-A7FF The association is aborted using A-ABORT and the 
    send job is marked as failed. The status is logged. 
    Error  Data Set does not 
    match SOP Class 
    A900-A9FF 
    Same as Refused above. 
    Error 
    Cannot  C000-CFFF 
    Same as Refused above.  
    						
    							HD9 1.1.x DICOM Conformance Statement 989605375630044 Rev. B Page 20   
       
    Understand 
    Warning 
    Coercion of Data 
    Elements 
    B000 
    Image transmission is considered successful. 
    Warning  Data Set does not 
    match SOP Class 
    B007 
    Same as Warning above. 
    Warning  Elements 
    Discards  B006 
    Same as Warning above. 
    * *  Any other 
    status code. 
    Same as Refused above. 
    The Behavior of Storage AE during communication failure is summarized in the Table below: 
    Table 4.2-9 
    STORAGE COMMUNICATION FAILURE BEHAVIOR 
    Exception Behavior 
    Timeout  The Association is aborted using A-ABORT and 
    the send job is marked as failed. 
    Association aborted by the SCP or network  layers The Send job is marked as failed.   
    A failed send job can be restarted by user interaction. The system can be configured to automatically resend failed jobs 
    if a transient status code is received. The delay between resending failed jobs and the number of retries is also 
    configurable. 
    4.2.1.3.1.4 SOP Specific Conformance for Storage Commitment SOP Class 
    4.2.1.3.1.4.1  Storage Commitment Operations (N-ACTION) 
    The Storage AE will request storage commitment for the conf igured device for instances of the Ultrasound Image, 
    Ultrasound Multi-frame Image and Structured Report Storage SOP Classes. 
    The Storage AE will consider Storage Commitment failed if  no N-EVENT-REPORT is received for a Transaction UID 
    within a configurable time period afte r receiving a successful N-ACTION response (duration of applicability for a 
    Transaction UID). 
    The Storage AE does not send the optional Storage Media  FileSet ID & UID Attributes or the Referenced Study 
    Component Sequence Attribute in the N-ACTION. 
    The Behavior of Storage AE when encountering status codes in  an N-ACTION response is summarized in the Table 
    below: 
    Table 4.2-10 
    STORAGE COMMITMENT N-ACTION RESPONSE STATUS HANDLING BEHAVIOR 
    Service Status  Further Meaning  Error Code  Behavior 
    Success Success  0000 The request for storage comment is considered 
    successfully sent. The system waits for the 
    association of the N-Event-Report. 
    * * 
    Any other 
    status code. The Association is aborted using A-Abort and the 
    request for storage comment is marked as failed. 
    The behavior of Storage AE during communication failure is summarized in the Table below:  
    						
    All Philips manuals Comments (0)

    Related Manuals for Philips Hd9 Owners Manual