VCT Vision ELITE Series Especificaciones Pagina 43

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 157
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 42
GE H
EALTHCARE
D
IRECTION
DOC0500644, R
EV
4 D
ISCOVERY
, L
IGHT
S
PEED AND
B
RIGHT
S
PEED
DICOM C
ONFORMANCE
S
TATEMENT
43 of 157
removable media using other application entities. These instances are external to this
conformance claim and the origin of SOP instances is outside the scope of this claim.
The MOD Archive Server AE can initialize Media by acting as an FSC to create a new DICOM
File-set on a 2.3GB MOD media or a 1.2GB MOD media. It initializes the DICOM File-set and
writes the specified SOP instances onto the MOD. The SOP instances written will be limited to
instances that match the criteria of one of the Application Profiles that is supported. When
updating media, a pre-existing File-set will be updated with the selected SOP instances that
match one of the supported Application Profiles.
3.2.2 Functional Definitions of AE's
This Server has only one Application Entity: the MOD Archive Application.
The MOD Archive Application can perform these functions:
It can initialize (create DOS filesystem) a piece of media, writing a new label and DICOM
File-set onto the media. (“LABEL”)
It can update a piece of media by adding new SOP instances to an already existing DICOM
File-set from local storage. (“SAVE”)
It can display a directory listing of the File-set on a piece of media. (QUERY)
It can copy SOP instance from the MOD onto local storage. (“RESTORE”)
3.2.3 Sequencing of Real World Activities
The updating function can only be performed on a piece of media that has already had a
DICOM File- set created.
The display function can only be performed on a piece of media that has already has a DICOM
File-set created. With no SOP instances having been added, the directory will be displayed
empty.
The copy function can only be performed with a piece of media that has been updated and has
DICOM SOP instances in the File-set.
There are no other sequencing requirements.
3.2.4 File Meta Information for Implementation Class and Version
The File Meta-Information for this implementation is:
File Meta-Information Version...................... 1
LightSpeed Implementation UID .................. 1.2.840.113619.6.55
Implementation Version Name..................... Helios Ver1
Vista de pagina 42
1 2 ... 38 39 40 41 42 43 44 45 46 47 48 ... 156 157

Comentarios a estos manuales

Sin comentarios