Syngo Siemens Errores – Fill Out and Use This PDF

Page 2 of 56

Effective Date: May 2013

Rev: 01

Page 3 of 56

Effective Date: May 2013

Rev: 01

Improper server hardware or software configuration settings or improper server

operating system (Server software defect)

Data loss: undetected failure to store image or patient data sent from

acquisition device requires patient to repeat exam

Data loss: loss of image data due to failure to back up

Loss of database backup data due to failure to back up database (either

tape or disk backup)

CAUTION

♦ If images are not archived on a regular basis, there may be data loss.

SYNGO®Dynamics software archives images automatically, if there is an

archiving device and it is properly configured and functioning. To prevent

data loss, Siemens requests that all customers have an archiving device

connected and check that it is functioning properly. United States Federal

law restricts this device to sale by or on the order of a physician.

User Profiles

The following profiles may vary depending on the site, qualifications, and personal

responsibilities. They should be considered general guides.

Technologist

The technologist is responsible for quality assurance of images, including the

preparation of images for reading. This preparation includes manipulation of image size,

position, or windowing values; creation of preliminary markers or measurements;

generation of additional result series, for example, parallel ranges; and sending data for

archiving.

Technologist must have the proper training, work experience, product training

certification or comparable product experience.

Physician

The physician performs the imaging examination, reporting of patient images,

completing and / or verifying reports, interventions, and justifying indications. The

physician is responsible for the safety of patients.

The physician must be a doctor of medicine and have the proper training, work

experience, and product training certification or comparable product experience.

Clinical Administrator

The clinical administrator configures application settings, DICOM nodes, archiving, and

manages short term storage and licenses, performs patient data administration, and is

the first support contact for reading physicians.

The clinical administrator is an application specialist who has work experience, product

experience, and knowledge of the clinical workflow.

IT Administrator

The IT administrator is responsible for data security, data protection, user management,

configuration of DICOM nodes, as well as backup and archiving. The IT administrator

manages the IT infrastructure of the clinical network, and is responsible for the

Page 5 of 56

Effective Date: May 2013

Rev: 01

Contents

1.

Introduction

8

1.1.

Purpose

8

1.2.

Scope

8

1.3.

Abbreviations

8

2.

Report Upload to OPENLink Option

11

2.1.

HL7 Message Details Message Specifications

11

2.2.

syngo® Dynamics Report Format

11

2.3.

Default Segment Listing

11

3.

Report Upload Message Examples

14

3.1.

syngo® Dynamics Report with standard linefeed substitution

14

4.

IHE DRPT REPORT CREATOR

15

5.

IHE DRPT Message Examples

16

6.

ADT Interface

17

6.1.

Message Overview

17

6.2.

Segment Structure

21

7.

Order Interface

24

8.

sDIS

26

9.

Connectivity:

26

10.

HL7 MESSAGES FOR VA10 sDIS INBOUND

27

11.

HL7 MESSAGES FOR VA10 sDIS OUTBOUND

28

12.

MESSAGE SEGMENTS

28

13.

Appendix A -Sample sDIS HL7 Messages

38

13.2. NACK Scenarios currently handled by sDIS

39

Appendix B – sDIS validations

41

Appendix B – Configuration files for ADT/ORM option

50

Page 7 of 56

Effective Date: May 2013

Rev: 01

(DR)

Short for Demographic Reconciliation in this document.

(OA)

Short for Order Association in this document.

ACK

Acknowledgment

ADT

Patient administration messages within the HL7 standard. Typically initiated

by the HIS to inform ancillary systems that a patient has been admitted,

discharged, transferred, merged, that other demographic data about the

patient has changed (name, insurance, next of kin, etc.) or that some visit

information has changed (patient location, attending physician, etc.).

ADT^A01

An HL7 Admit/Discharge/Transfer message for Patient Admit. This occurs

when the patient is admitted to the hospital.

ADT^A04

An HL7 Admit/Discharge/Transfer message for Patient Registered. This

occurs when the patient is registered at the hospital.

ADT^A08

An HL7 Admit/Discharge/Transfer message for Patient Update. This occurs

when the patient’s demographic information has been updated from what was

previously sent when the patient was admitted.

ADT^A18, A34, A40

An HL7 Admit/Discharge/Transfer message for Patient Merge. These are

Page 8 of 56

Effective Date: May 2013

Rev: 01

syngo® Dynamics HL7 Interface Specifications Manual

used when two different identifications for the same patient are found and

need to be merged into one identification.

AL1

Allergy Information

All servers

For the purposes of this document, the term “all servers” refers to all syngo

Dynamics servers that are included in the multi-server login configuration of

the current server.

CA

The order control code for the order that is canceled. It is used in ORC

segment of HL7 ORM Message

DDI

Data Dictionary Item

DG1

Diagnosis

DOB

Patient date of birth

Enterprise

For the purposes of this document, the term “enterprise” refers to the

collection of all departments on all servers that are included in the multi-server

login configuration of the current server.

The scope of “enterprise” is not defined as all departments of all syngo

Dynamics servers that are physically located in an institution.

Each syngo Dynamics server within an institution server pool has its own

enterprise scope, as the scope is defined by the multi-server login

configuration of that individual server.

FON

Short for Filler Order Number in this document - The order number assigned

to the Service Request by the party filling the order.

HIS

Health Information System

HIS Verification

A method used by the syngo Dynamics Server’s Vault services to reconcile

patient/study information by using a DICOM Modality Worklist Server to

confirm scheduled study data. Both automatic and manual reconciliation

methods are supported.

HL7

Specific message standards created by the Health Level Seven organization

for the exchange, management and integration of electronic healthcare

information.

IE

Interface Engine

IP

Internet Protocol

M

Mandatory for sDIS

Master Patient Index

Master Patient Index (MPI) is an index which references all existing patients

registered at a health care organization in such manner that each patient is

logically represented only once and can be uniquely identified. Use of MPI

allows clinical and demographic information to be cross-referenced between

different facilities within the enterprise of a health care organization.

MPI can be a specific SID/PID pair among all SID/PID pairs that are assigned

to a patient. For example, for a health care organization that defines “EPI” as

the MPI SID, the value “123456789^^^EPI” indicates it is a MPI and

“123456789” is the MPI PID.

MPI

Master Patient Index (MPI) is an index which references all existing patients

registered at a health care organization in such manner that each patient is

logically represented only once and can be uniquely identified. Use of MPI

Page 9 of 56

Effective Date: May 2013

Rev: 01

allows clinical and demographic information to be cross-referenced between

different facilities within the enterprise of a health care organization.

MPI can be a specific SID/PID pair among all SID/PID pairs that are assigned

to a patient. For example, for a health care organization that defines “EPI” as

the MPI SID, the value “123456789^^^EPI” indicates it is a MPI and

“123456789” is the MPI PID.

MRG

Merge

MRN

Medical Record Number in HL7 (Same as Patient ID in DICOM)

MSH

Message Header

NACK

Negative Acknowledgement

NK1

Next of Kin

NW

The order control code for new order that is used in ORC segment of HL7

ORM Message

O

Optional for sDIS

OBR

The Observation Request segment that HL7 ORM message uses to transmit

information specific to an order for a diagnostic study or observation, physical

exam, or assessment.

ORC

The Common Order segment that HL7 ORM message uses to transmit fields

that are common to all orders

ORM^O01

An HL7 General Order Message. Also referred to as an “Order” or “HL7

Order” in this document.

PID

Patient ID or refers to the patient identification segment in a HL7 message.

PON

Short for Placer Order Number in this document - the order number assigned

to the Service Request by the party placing the order.

PV1

Patient visit segment in a HL7 message which includes the patient class.

RP-RO

The order control code used for the order that is replacing the previous one. It

is used in ORC segment of HL7 ORM Message. For each replacement order,

ORC segment use ORC-1-order control value of RP, followed by another

ORC segment with ORC-1-order control value of RO.

sDIS

syngo Dynamics Information System Features

SID

Site ID. Another name for an Assigning Authority (e.g. an Information System)

from the HL7 Standard.

SID/PID

A Site ID and Patient ID combination.

SIU

Scheduling Information Unsolicited

UI

User Interface

WB

sDIS Whiteboard

Page 10 of 56

Effective Date: May 2013

Rev: 01