SCCIPA

AxSys Technology Limited
SCCIPA Hospital Interface Specification
AxSys Project: SCPA-001 (Phase 2)
Project Code:
SCPA-001
Document Name:
SCCIPA Hospital Interface Specification
Document Version:
2.22
Document Status:
Draft
Date Last Modified:
3rd May 2012
Document Owner:
Razwan Sarwar
Lead Reviewer:
Sreedhar T , Brian Heraty, Dean Burton
Distribution List:
AxSys Project Team, SCCIPA Team
SCCIPA Hospital Interface Specification (SCPA-001)
v2.22
p1 of 90
Contents
1. DOCUMENT CHANGE CONTROL FORMS................................................................................................ 4
1.1 Release Notes............................................................................................................................................. 4
1.2 Change Control.......................................................................................................................................... 5
2 INTRODUCTION............................................................................................................................................. 7
3 OVERVIEW AND WORKFLOW OF COMPONENTS..................................................................................... 8
3.1 Overview of the initial release of the Hospital Interface.........................................................................8
3.2 Overview of OConnor/St. Louise Hospital Interface..............................................................................8
3.3 Overview of the File Locations............................................................................................................... 10
3.4 Processing Messages to Backup Directory...........................................................................................10
3.5 Non-functional Requirements................................................................................................................. 10
4 TECHNICAL OVERVIEW............................................................................................................................. 11
4.1 Local Environment................................................................................................................................... 11
5 DETAILED TECHNICAL SPCIFICATION..................................................................................................... 12
5.1 Physical Component & Server Diagram................................................................................................. 12
5.2 Process Flow Diagram............................................................................................................................. 12
5.3 Mirth Connect Process Flow Diagram.................................................................................................... 13
5.4 Bespoke Components............................................................................................................................. 14
5.5 Overview of HL7 Message & Process Flow........................................................................................... 14
6 PATIENT MATCHING RULES...................................................................................................................... 15
7 ACK.............................................................................................................................................................. 17
8 ADT............................................................................................................................................................... 18
8.1 ADT Process Flow Diagram..................................................................................................................... 19
8.2 Processing Details................................................................................................................................... 20
8.3 Patient Match Rules................................................................................................................................. 20
See section 5 of this document for Patient Match Rules............................................................................20
8.4 ACK........................................................................................................................................................... 20
8.5 Segments Expected................................................................................................................................. 20
9 RAD.............................................................................................................................................................. 28
9.1 RAD Process Flow Diagram.................................................................................................................... 29
9.3 Reporting Requirements......................................................................................................................... 29
9.4 ACK........................................................................................................................................................... 29
9.5 Segment Details....................................................................................................................................... 29
9.6.1 PROCESS RAD HL7 RESULTS TO EXCELICARE.......................................................................................34
9.7 RADIOLOGY Report Special form mapping........................................................................................... 37
10 LAB............................................................................................................................................................. 38
v2.22
p2 of 90

10.1 Segments Expected............................................................................................................................... 39
10.2 LAB Process Flow Diagram.................................................................................................................. 40
10.3 Processing Details................................................................................................................................. 41
10.4 ACK......................................................................................................................................................... 41
10.5 Segment Details..................................................................................................................................... 41
11 MDM............................................................................................................................................................ 48
11.1 MDM Process Flow Diagram................................................................................................................. 49
11.3 ACK.......................................................................................................................................................... 50
12 PATH........................................................................................................................................................... 54
12.1 PATH Process Flow Diagram................................................................................................................. 56
12.3 ACK......................................................................................................................................................... 57
13 PROCESSING AND TESTING OF MESSAGES........................................................................................ 64
13.1 Expected Volume of Data...................................................................................................................... 64
13.2 Minimum Processing Time.................................................................................................................... 64
13.3 Testing Requirements............................................................................................................................ 64
14 ADDITIONAL REQUIREMENTS................................................................................................................ 65
15 APPENDIX A ACE SCREENS................................................................................................................. 66
16 APPENDIX B HL7 REFERENCE FOR RADIOLOGY REPORT.............................................................. 71
16.1 Reports - Discharge Summary HL7 v. 2.3 Sample...............................................................................71
16.1 Reports - History and Physical HL7 v. 2.3 Sample..............................................................................74
17 APPENDIX C HL7 HL7 MESSAGE RESULT SAMPLES........................................................................ 77
17.1 ADT (Admit, Discharge, Transfer) HL7 v. 2.2 Sample..........................................................................77
17.2 Laboratory Result HL7 v.2.1 Sample.................................................................................................... 77
17.3 Microbiology Result HL7 v. 2.1 Sample................................................................................................78
17.4 Radiology Result HL7 v. 2.1 Sample..................................................................................................... 78
18 APPENDIX D ERROR DESCRIPTION.................................................................................................... 79
19 APPENDIX E HOSPITAL SERVICE........................................................................................................ 81
20 APPENDIX F COUNTRY CODES............................................................................................................ 83
v2.22
p3 of 90
1. DOCUMENT CHANGE CONTROL FORMS

1.1 Release Notes
Versio
n
Status
1.0
Notes
Date
Issued
Owner
Supersede
d
22nd March
2011
DB
2.0
Supersede
d
13th March
2011
DB
2.17
Supersede
d
Correction of inaccuracies in spec.
06/17/201
1
BH
2.18
Draft
(internal)
Not issued
RS
2.19
Draft
(internal)
Not issued
RS
2.20
Draft for
review
Updated document to introduce

OConnor and incorporate Mirth as a
transport engine. Note that Good
Sam/RMCSJ will remain as per the
original implementation at this stage.
04/24/201
2
RS, BH
2.21
Draft for
review
Updated diagram in section 4.3 and

modified text to reflect discussion with
SCCIPA on 04/26/2012.
04/27/201
2
RS,BH
2.22
Released
Updates following review with DB
05/03/201
2
BH
v2.22
p4 of 90

1.2 Change Control
Note: This section will not be updated for draft documents.
Changes made from: 2.17 to 2.20
N
o
Sections Impacted
Change Made
Changes throughout the spec to accommodate the use of
the Good Sam adaptors re-configured for OConnor / St.
Louise.
The main changes are: Secondary identifiers to be used for matching need
to be determined from the message (using MSH.4)
Secondary identifiers inserted on import of an ADT
message need to be inserted to the identifiers
appropriate to the source of the message.
Source field as entered on Special Forms needs to
be determined from MSH.4
Mirth will be used to provide the transport layer for
messages from OConnor/St. Louise.
Messages will be pre-processed by Mirth to ensure
that fields such as MSH.3 are set to an appropriate
value to avoid uncertainty in the value that may be
received from different sources.
Changes made from: 2.20

N
o
Sections Impacted
Change Made
2.2
Indicate separate queues and queue readers for OConnor /

St Louise following BH discussion with SCCIPA.
2.3
Update folder paths for drop folders
4.3
Updated diagrams to reflect separate queues for OConnor

and St. Louise.
Various
Updates following review and to reflect discussion with

SCCIPA on 04/26/2012.
Changes made from: 2.21

N
o
Sections Impacted
Change Made
5.4
Update to indicate that there is one component for each

message type
Update to include IN1.2 in derivation of the Insurance ID

used for patient matching.
8.5 (ADT PID),

9.5 (RAD PID),
10.5 (LAB PID),
11.4 (MDM PID),
Updated the entry for PID.2 to indicate that this field is not
mapped.
v2.22
p5 of 90

12.4 (PATH PID)
4
8.5 (ADT PV1)
Moved description of processing of clinician name from

Notes section to the Map To column for PV1.7
9.2
Remove reference to updating Account Number Patient

Details are not updated by the RAD message.
Include note re Radiology Results written to hidden
Department and that they are viewed in CCD
10.5 (LAB OBR)
In Notes section, removed sentence referring to HCALab,

HCAMic, HCARad, this information isnt used in the interface. The
type of result being reported is determined from MSH.3
11.4 (MDM PV1)
Moved description of processing of clinician name from

Notes section to the Map To column for PV1.7
11.4 (MDM TXA)
Changed TXA.3 to TXA.8 (the incorrect field reference had

been used for the Last Edited Date)
12.4 (PATH OBX)
Clarify that a report is re-constituted from the OBX.5

entries (as opposed to referring to a document).
For information or help regarding this document, please contact the AxSys Project Team:
AxSys Technology Ltd., AxSys House, Glasgow Business Park, Marchburn Drive, Paisley, PA3 2SJ
Tel:
0870 084 8600
Email: dean.burton@axsys.co.uk
v2.22
p6 of 90

2
INTRODUCTION
This document specifies the details of the Hospital Data interface into the AxSys Health
Information Exchange (HIE) Hub. The interface processes a number of HL7 messages of
different types.
The 2.20 release of this document builds on the initial release of the interface to accommodate
the OConnor and St Louise hospitals (Duaghters of Charity group) by creating copies of the
message adaptors developed for the Good Samaritan interface and reconfiguring them for
OConnor and St. Louise. The initial release of the interface will remain in place to process the
HL7 messages from the Good Sam / RMCSJ hospital group.
The hospital Interface is based on a file drop into target folders (one per message type). While
the initial release of the interface had discrete file listener services for each drop folder, the file
listening for the OConnor interface will use Mirth to receive the files and queue them to the
appropriate message type adaptor. Mirth will also handle the ACK file processing such that there
is no apparent change to the sending end of the interface.
The preparation for the OConnor / St Louise processing has endeavoured to ensure that the
messages are as similar as possible to the Good Sam / RMCSJ messages, it should be noted
that the introduction of Mirth provides the flexibility to carry out further pre-processing at the
Excelicare end of the interface thus maximising the possibility that the OConnor/St. Louise
messages can be presented to the adaptors in the same format as the Good Samaritan
messages.
v2.22
p7 of 90

3
OVERVIEW AND WORKFLOW OF COMPONENTS
f the initial release of the Hospital Interface

Currently HL7 messages are picked up from the ECLIVE-MEDICITY server in the SCCIPA server
environment. (The IP-Address of this server is defined separately from this document). Each
message sent is placed into its own folder location and picked up by a file listener in real time.
Processing is carried out by the AxSys Exceliport Integration Server.
Processed message types for the initial release of the interface (Good Samaritan / RMCSJ
hospital group) are:
ADT
LAB
RAD
MDM
PATH
There are two folder structures for file drop and backup.
Each incoming message is placed in the message type folder in the file drop structure that
corresponds to that particular message sent from the source system. For example, an incoming
ADT message will be dropped into the ADT drop folder. A separate file listener service for each
folder picks up incoming messages and processes them. Processed messages are moved into
the appropriate folder. The file listener service for a specific message type is configured to place
the received message onto a dedicated Microsoft Message Queue (private queue) for that
message type. Queue processing services are also configured to process each message through
the adaptor for the corresponding message type. The adaptor writes the received data into the
HIE according to the mapping defined in this specification.
f OConnor/St. Louise Hospital Interface

The data transport for files coming from OConnor / St Louise hospital will be handled by
deployment of the Mirth Connect engine.
Mirth will be in place to act as the transportation mechanism to receive files and place them on
the relevant queues for processing.
Five new (private) queues will be created for each hospital (OConnor and St Louise) although
it must be noted that the messages from these two hospitals will be received in a single feed. A
new adaptor will be introduced for each queue. The message types expected in the OConnor /
St Louise hospital feed are:
ADT
LAB
RAD
MDM
PATH
Drop zone folders will be created for each message type and the received messages will be
pushed into the appropriate existing queue according to message type.
v2.22
p8 of 90

The interface process is as follows:
The files from OConnor / St Louise hospital will have to be dropped into folders as per
the folder structures defined in section 3.3 of this document.
Mirth channels will be defined to listen to each folder.
Each Mirth Channel will assume the message type from the drop folder to which it is
listening. MSH.4 will be used to determine whether the message is placed on the
OConnor queue for that message type, or on the St. Louise queue.
This interface is based on the following fundamental assumption:o

o
When a LAB, RAD, MIC or PATH message is received it will contain LAB, RAD,
MIC or PATH as a substring of the MSH.3 field.
Unique, fixed identifiers will be used in MSH.4 to indicate whether the message is
sourced form OConnor Hospital or St. Louise Hospital.
Once a message has been received an Acknowledgement will be written to the ACK
folder within the OConnor hospital file structure (refer to section 3.3). The Diagram in
section 5.3 illustrates the Mirth process. Acknowledgements will comply with section 7 of
this document.
The queue readers for OConnor and St. Louise will be created as copies of the Good Samaritan
Queue Readers. The following changes will be incorporated into the queue readers as new
features required to achieve the OConnor / St. Louise integration:
The Source will be derived based on the value of MSH.4. This will be used when creating
Special Form records as part of the data import process. Records created from messages
from OConnor Hospital will have the Source field set to OConnor and records created
from messages from St. Louise Hospital will have the Source field set to StLouise.
the match rules will be applied according to the source of the message this is
necessary because the nature of the MRN and URN (PID.3 and PID.4) will vary with
source such that the secondary identifiers in Excelicare (as used for matching) will be
different for each source. In particular, the ADT adaptor will have to be modified to
dynamically determine which secondary identifiers need to be inserted from PID.3 and
PID.4 (note that only the ADT adaptor inserts identifiers from PID.3 and PID.4 and only
if the values do not exist for that source).
Once a message has been placed into the appropriate queue the processing will be carried out
by the OConnor/St. Louise adaptors (one per message type, per source) provided within the
AxSys Exceliport Integration Server.
3.3 Overview of the File Locations
The current file structure setup for messages from the Good Samaritan/RMCSJ hospital group
will be left unchanged. Files will be dropped into the following folders:Message Type
ADT
LAB
RAD
MDM
PATH
Drop Folder
D:\Ax_Medicity\SCIPPA\ADT
D:\Ax_Medicity\SCIPPA\LAB (Labs messages)
D:\Ax_Medicity\SCIPPA\MIC (Microbiology messages)
D:\Ax_Medicity\SCIPPA\RAD
D:\Ax_Medicity\SCIPPA\REPORTS
D:\Ax_Medicity\SCIPPA\PATH
v2.22
p9 of 90

OConnor / St Louise hospital will have to conform to the file structure in the following table.
Message Type
ADT
LAB
RAD
MDM
PATH
Acknowledgment
Processed Files
Failed Files
Drop Directories
D:\Ax_Medicity\OConnor_StLouise\ADT
D:\Ax_Medicity\ OConnor_StLouise\LAB (Labs messages)
D:\Ax_Medicity\ OConnor_StLouise\MIC (Microbiology messages)
D:\Ax_Medicity\ OConnor_StLouise\RAD
D:\Ax_Medicity\ OConnor_StLouise\REPORTS
D:\Ax_Medicity\ OConnor_StLouise\PATH
D:\Ax_Medicity\ OConnor_StLouise\ACK
D:\Ax_Medicity\ OConnor_StLouise\Processed
D:\Ax_Medicity\ OConnor_StLouise\Failed
3.4 Processing Messages to Backup Directory

Once a message has been processed, the file will be moved, by Mirth, from the drop folder to
one of the two backup folders detailed in the table below.
Folder Name
Processed
Failed
Description
Files that have been successfully queued for the appropriate Queue Reader
are dropped into this folder
Files that cannot be queued are moved into this folder.
3.5 Non-functional Requirements

This interface will report all actions taken to enable users to track what is happening within the
interface on a day to day basis. Each time an HL7 message is processed it will be logged, along
with any matches made or failed, and any data created within Excelicare. Authorised users will
be able to re-process failed messages and view the results of processing from within the
Excelicare Message Manager Module.
v2.22
p10 of 90

4
TECHNICAL OVERVIEW
4.1 Local Environment
OConnor/St. Louise Hospital Interface
Source System Vendor

Type of Interface (overview)
Connection type
Network environment
Firewalls
Security
Data retrieved
Typical Usage
Medicity
Population of CCD with ADT, Laboratory, Pathology, Radiology
and Report data
File Transfer
Unknown
None
None
ADT, LAB, RAD, MDM, PATH, MIC
Up to 1800 records (typically) per hospital group per day in real
time
Other information
v2.22
p11 of 90

5
DETAILED TECHNICAL SPCIFICATION

5.1 Physical Component & Server Diagram
Figure 1- System Layout

5.2 Process Flow Diagram
The diagram below illustrates the process and components involved in importing the HL7 messages for Good
Samaritan using the existing discrete file listener services and OConnor / St Louise using Mirth.
Figure 2 Message Process Diagram

v2.22
p12 of 90
5.3 Mirth Connect Process Flow Diagram

This diagram illustrates the process of Mirth listening and receiving files. Mirth channels will be
set up within the ECPROTST and EC LIVE SCCIPA environments, for each message type for the
OConnor / St Louise feed. Mirth will actively listen for incoming messages in real time.
Once Mirth has read a message from a drop folder, the Mirth file listener will generate an
acknowledgement and write it back to the ACK folder.
MSH.3 and MSH.4 will be read by the Mirth channel and used to determine, which queue the message will be
written to.
Figure 3 Mirth Connect Process Diagram
v2.22
p13 of 90

5.4 Bespoke Components
All the components of this interface will run on the Exceliport (EP) server. There will be one
interface component per message type and each will be named according to the message type
processed.
AxEPProcessHL7Result
Purpose
Component to process HL7 Result messages and import to Excelicare.
Language / Version
VB.NET .NET 3.5
Called By
AxEPQueueReader
Dependencies
AxEPEventLog, AXEPDAL, Labs API, CDD importers, MSMQ, SQL
Server(Not on Service Startup)
Config Parameters
Patient Match Type ID, MSMQ Name
Notes
Patient match and importing will be done using Labs API
5.5 Overview of HL7 Message & Process Flow

The received HL7 Messages will be extracted and processed. The processing of each message
type is detailed in the following sections. Patient matching will be done in a consistent manner
across all message types.
If the patient is found in Excelicare, the message will be imported into the matched patient
record using the rules detailed for each message type.
If a Patient is not found then the message will be treated as failed and will be logged with a
failure message into the Exceliport Database Log Tables, these reports can be viewed from the
Message Manager module. The message will detail that the patient did not exist.
Note 1: The Labs API is used for all types of diagnostic lab and radiology results, which are
imported into the Excelicare Results tables (called Labs). It should be noted that these
tables/columns refer to labs to cover both laboratory and radiology tests. The Radiology
Results data will also be added to the CCD Radiology Special Form which will be displayed to
users via the CCD.
Note 2: Messages received from the Good Samaritan/RMCSJ Hospital group must have the
source field on the target CCD form(s) set to Good Samaritan / RMCSJ
Note 3: Messages received from the OConnor/St. Louise Hospital group must have the source
field on the target CCD form(s) set to OConnor or StLouise as appropriate to MSH.4
Also note that any Z segments found in the messages will be ignored unless otherwise stated
i.e. the data contained within the Z segment(s) will not be processed into the HIE.
v2.22
p14 of 90

6
PATIENT MATCHING RULES
Patient matching will be undertaken using the following segments. The data in the PID section
will be matched against the Excelicare Patient using the defined Match Rule; the match rule will
be defined through the configuration screen using the Exceliport Admin Utility.
The IN1 segment is not imported into Excelicare but IN1.2 (Insurance plan ID) and IN1.36
(Insurance Policy Number) are used as part of the Patient Matching Rules. The matching data
will be present in the SCCIPA Excelicare database from the members Interface.
The table below shows the Patient Identifier fields in the HL7 PID and IN1 segments that will be
used for Patient Matching.
Segment ID
PID.3
Element
Name
Medical
Record
Number
Comments
PID.4
Medical
Record URN
PID.5.1
Last Name
Patient Identifiers <hospital> MRN (where <hospital> is Good

Samaritan or OConnor or St. Louise)
If a match is made and the MRN is not populated in EC then the
<hospital> MRN will be loaded to the corresponding secondary
identifier in the patient record from the incoming message.
Patent Identifiers <hospital> URN (where <hospital> is Good
Samaritan or OConnor or St. Louise)
If a match is made and the URN is not populated in EC then the
<hospital> URN will be loaded to the corresponding secondary
identifier in the patient record from the incoming message
|<Surname>^^^^^|
PID.5.2
First Name
|^<Forename>^^^^^|
PID.5.3
Middle Name
|^^<Middle Name>^^^^^|
PID.7
Date Of Birth
Format: YYYYMMDD
PID.8
Gender
Coded field.
IN1.2
Insurance plan
ID
Insurance ID
Number
Payers Health Payer ID Taken from Insurance segment (IN1)
IN1.36
Payers Health Plan Number Taken from Insurance segment

(IN1)
When a patient match is successful between the PID section and an Excelicare HIE Patient the
data contained within the rest of the HL7 file will be imported into the HIE.
If a Patient is not found then the message will be treated as failed and will be logged with a
failure message into the Exceliport Database Log Tables, these reports can be viewed from the
Message Manager module. The message will detail that the patient did not exist.
Match Rules:
The incoming ADT HL7 message will have the following match rules applied:
1. URN (i.e. match incoming PID.4 against the URN secondary identifier for the hospital
from which the message was received), Patient Last name, First Name, Middle Initial,
Date of Birth, Gender and Insurance ID Number.
2. MRN (i.e. matching incoming PID.3 against the MRN secondary identifier for the hospital
from which the message was received), Patients Last Name, First Name, Middle Initial,
Date of Birth, Gender and Insurance Number.
3. Patients Last Name, First Name, Middle Initial, Date of Birth, Gender and Insurance ID
Number.
4. Patients Last Name, First Name, Middle Initial, Date of Birth and Gender.
v2.22
p15 of 90

Notes
URN and MRN will be added to the patients record from the incoming ADT message.
The first time an ADT message is received for a patient via a hospital interface these
fields will be undefined in the patient record. MRN and URN will be mapped to the
appropriate secondary identifiers.
It should be assumed that for most hospitals the MRN format will be distinct and hence a
discrete MRN secondary identifier will be required for each hospital. However, the
hospitals function within parent groups and hence multiple hospitals will share the same
URN format. The change to the adaptor
Insurance ID (from IN1.2 / IN1.36) will be compared with the HMOID identifier in
Excelicare ACE for the purposes of patient matching.
v2.22
p16 of 90

7
ACK
MSH|^~\&||COCQA1A|||200810230831||ADTÂ03|QA1AGTADM.1.149118|D|2.1
ACK (Acknowledgement) files are sent in response to all messages. The ACK file for messages
from the Good Samaritan/ RMCSJ hospital group are written to the following folder:
D:\Ax_Medicity\SCCIPA\ACK
New hospitals added will have the Acknowledgement (ACK) written to the hospital specific ACK
folder:
D:\HospitalDataFiles\<hospitalName>\ACK
It will be the responsibility of SCCIPA to manage the ACK files to ensure:1. They are routed to the appropriate ACK folder agreed with the sender.
2. Housekeeping to avoid unnecessary, long term consumption of disk space.
MSH Segment
Notes:
Note that the first | is an indication of the field separator the chars up to the next field separator are the
delimiters. So, for this message
MSH.1 = |
MSH.2 = ^~\&
MSH.3 = blank
Etc
Example:
MSH|^~\&||COCQA1A|||200810230831||ACKÂ03|QA1AGTADM.1.149118|D|2.1
Item
MSH.3
MSH.4
MSH.5
MSH.6
MSH.7
MSH.9
Field
Sending Application
Sending Facility
Receiving Application
Receiving Facility
Date time of Message
Message Type
MSH.10
Message Control ID
MSH.11
Processing ID
Details
Set to be the current date time.

MSH.9.1 = ACK
MSH9.2 is taken from MSH.9.2 of the message
received.
This data item is taken from the incoming
messages and copied to the ACK.
Set to
P for production environment and
D for non-production.
MSA Segment Message Acknowledgement

Notes:
Example:
MSA|AA|PAGTADM.1.35358
Item
Field
MSA.1
Acknowledgment Code
MSA.2
Message Control ID
Details
AA success
AE Error
AR Reject
This data item is taken from the incoming message
segment MSH.10 then copied to the ACK
(Acknowledgement).
v2.22
p17 of 90

8
ADT
EVN|A03|200810230831
PID|1||J000106655|J107307|DAILEYÂDMIT^^^^||19740926|F|^^^^^||144 PARKERS CHAPEL
RAOD^^PORTLAND^TN^37148ÛSA^^^SUMNER||(615)491-4187|(615)344-9551|ENGLISH|M|BAP
|J00008034580
PV1|1|I|J.3N^J.190^3|EL|||SEXTON^SEXTON^MELISSA^^^^MD||SEXTON^SEXTON^MELISSA^^^^
MD|MED||||CR||Y|BREME^Brewington^Melissa^^^^MD|IN||TODD||||||||||||||||HOM|||COC
QA1A|TEST|DIS|||200810221551|200810230831
ACC|20081022^|11
GT1|1||DAILEYÂDMIT^^^^||144 PARKERS CHAPEL RAOD^^PORTLAND^TN^37148ÛSA^^^SUMNER
|(615)491-4187||19740926|F||SA|213-45-6547|||HCA THE HEALTHCARE COMPANY|P.O. B
OX 550^^NASHVILLE^TN^37202-0550|(615)344-9551|||F
GT1|2||^^^^^||^^^^^^^^|||||||||||^^^^
IN1|1|AETNA||AETNA|10 WHITE STREET^ÂNYTOWN^TN^00111ÛSA||6155551212|AETNA GROUP
#|AETNA GROUP NAME|||||||DAILEYÂDMIT^^^^|01|19740926|||||||||||||||||||||||||F
UP||||19740926||F
v2.22
p18 of 90

8.1 ADT Process Flow Diagram
The following diagram describes the processes involved in reading ADT messages from the ADT
message queue; refer to processing details in section 8.2 for process steps. Steps with an
e(number) label, for example e1, indicate that specific errors may be reported. Steps labelled
with a l(number), for example l1, indicate that messages may be logged to the database.
Refer to Appendix d error description for a full list of errors that may be reported.
Section 6 outlines patient matching rules.
For Next of Kin, Patient Visit matching rules are listed in section 8.5.
Figure 4 ADT Process Flow Diagram
v2.22
p19 of 90
8.2 Processing Details

ADT Messages will be triggered upon Admit, Discharge and Transfers related to the source
hospital group. ADT messages will contain hospital/group-specific IDs (MRN and URN) along
with Demographic and Insurance Information for each patient. Insurance information will be
used for matching purposes only.
Each ADT message that arrives will have an appropriate ACK sent.
The MSH header will be checked to make sure the right code is in MSH.11 to fit the
environment we are using.
Check MSH9.1 reads ADT if not then error message
Update Patient Details Identifiers if appropriate.
Find PID segment and use for patient matching
o If one match then proceed.
o If no match then log warning message into Exceliport Database Log Tables, that
patient was not found in HUB. Then end processing of this message.
o If more than one match then error message.
All segments processed as detailed. Segments expected to occur in the standard HL7 order.
8.3 Patient Match Rules
See section 6 of this document for Patient Match Rules.
8.4 ACK
The acknowledgement for this message will comply with that defined in the ACK section of this
document.
8.5 Segments Expected
Segment
MSH
EVN
PID
NK1
PV1
DG1
MRG
Description
Message Header
Event Type
Patient Identification
Next of Kin
Patient Visit
Diagnosis
Merge
Frequency
Only
Only
Only
Only
one
one
one
one
per
per
per
per
patient
patient
patient
patient
If messages assume a billing system as destination then these segments could be present:
Segment
PR1
GT1
IN1
ACC
UB1
Description
Procedures
Guarantor
Insurance
Accident
UB82 Data
Frequency
Multiple per patient
Only one per patient
MSH Segment Message Header

Notes:
Identifies the start of a message.
v2.22
p20 of 90

Note that the first | is an indication of the field separator. The chars up to the next field separator are the
MSH.1 = |
MSH.2 = ^~\&
MSH.3 = blank
etc
Example
Item
MSH.4
Field
Sending Facility
Details
The value of this field will be used to set the Source on all
CCD forms created by the received ADT message.
Note that this is introduced as a change for the OConnor
version of the adaptor. The Good Sam version of the
adaptor had a fixed source will not be changed.
For messages originating from OConnor Hospital it is
assumed that this field will contain OCON. SCCIPA have
yet to confirm the value that will be received in this field for
messages from St. Louise.
The Source entry on Special Forms created from the
import of messages will be set as defined in section 5.5.
MSH.9
Message Type
MSH9.1 ADT
MSH9.2:
A01 - admit / visit notification
A02 - transfer a patient
A03 - discharge/end visit
A04 - register a patient
A05 - pre-admit a patient
A06 - change an outpatient to an inpatient
A07 - change an inpatient to an outpatient
A08 - update patient information
A09 - patient departing - tracking
A11 - cancel admit / visit notification
A12 - cancel transfer
A13 - cancel discharge / end visit
A17 - swap patients (ignore)
A18 - merge patient information (ignore)
All these message type will be received.
MSH.10
Message Control ID
MSH.11
Processing ID
A17 and A18 will be ignored as this source is not the

source of truth for swaps and merges.
This data item is taken from the incoming messages and
copied to the ACK.
Check that this matches the environment we are writing
the data to:
P = Production
D = Non production
EVN Segment Event Type (Do

Notes:
not import)
Example:
EVN|A03|200810230831
Item
Details
Map To
PID Segment Patient Identification

v2.22
p21 of 90

Notes:
Any differences in the demographics will not cause an update to the data within SCCIPA Excelicare
other than in relation to the hospital MRN and URN identifiers. These values will be written to the
appropriate secondary identifiers if these are not already populated.
If the patient does not exist then the message is not imported and will be logged in such a way as to
indicate that it was not possible to match the patient.
There will be only one PID per ADT message.
No demographic information should be updated in Excelicare for matched patients.
Example:
PID|1||J000001414|J1749|TESTÎNTERFACE^^^^||19750421|F||||||||||J00000021977|
123-45-6789
Item
PID.2
PID.3
Details
LSS Encounter Number
Medical record Number
Map To
Not mapped.
Patient Identifiers:
The mapping to the identifier is source specific, i.e.
For Good Samaritan/RMCSJ
Map to Good Samaritan MRN
(secondary)Identifier.
MRN Format: Letter followed by 9 digits (e.g.
J000106655 no validation required.
For OConnor hospital (where MSH.4 indicates OConnor)
Map to OConnor MRN (secondary) Identifier.
MRN Format: 6 digits (e.g. 106655) no
validation required.
For St. Louise hospital (where MSH.4 indicates St Louise)
Map to StLouise MRN (secondary) Identifier.
MRN Format: to be defined no validation will be
required.
Note
1. Only load to the Excelicare Identifiers for the
patient if the corresponding Excelicare Identifier is
undefined. (This should be the case for the first
ADT message received for a patient).
PID.4
Medical Record Urn
Patient Identifiers:
The mapping to the identifier is source specific, i.e.
For Good Samaritan/RMCSJ
Map to HCA URN (secondary) Identifier
URN Format: Letter followed by any number of
digits (e.g. J107307) no validation required.
For OConnor/St Louise (i.e. MSH.4 indicates either
OConnor or St. Louise)
Map to OConnorStLouise URN (secondary)
Identifier
URN format: to be defined no validation will be
required
Note
1. Only load to the Excelicare Identifiers for the
patient if the corresponding Excelicare Identifier is
undefined. (This should be the case for the first
ADT message received for a patient).
v2.22
p22 of 90

PID.5
Patient Name
PID.7
PID.8
Patient DOB
Gender
PID.5.1 Last Name

PID.5.2 First Name
PID.5.3 Middle Name
PID.5.4 Suffix
PID.5.5 Title
PID.5.6 Degree (not imported)
Patient Date of Birth
Patient Gender.
M Male
F Female
U Unknown
PID.9
PID.10
Patient Alias
Race
Patient other name

Patient Ethnic Origin
PID.10.1 code
PID.10.2 Text
PID.10.3 Code scheme
PID.10.4 Alt code
PID.10.5 Alt Text
PID.10.6 Alt Code scheme
Note Interface should allow for up to six fields in PID 10,
but only PID.10.1 will be used. Code translation as per
table below.
PID.11
Patient Address
Code
Name
A
Asian Pacific Islander - Hawaiian
AI
Asian Indian
B
Black African American
H
Hispanic Other Latino
HB
Hispanic African American Ancestry
HW
Hispanic Caucasian Ancestry
I
Native American Alaskan Aleut
M
Multiracial
O
Other
U
Unknown
W
White - Caucasian
PID.11.1 address line 1
PID.11.3 city
PID.11.4 State
PID.11.5 Zip
PID.11.6 Country - Appendix f country codes provides
the relevant mapping codes.
PID.11.7
PID.11.8
PID.11.9 County
The address here is recorded as the patients current
address.
PID.13
PID.14
PID.16
Patient phone
Patient phone business
Marital Status
Patient home phone number

Patient Business phone number
Patient Marital Status
PID16.1 - Code
Code
D
Name
Divorced
v2.22
p23 of 90
PID.18
PID.19
Patient Account Number

SSN Number
M
Married
S
Single
U
Unknown
W
Widow/Widower
X
Legally Separated
P
Life Partner
Patient Identifiers Source Account Number
Patient Identifiers - SSN
NK1 Segment Next of Kin

Notes:
Update and add NOK as details here require. Add to contact details.
To match NK segment with existing records in Excelicare use NK1.2: Name, NK1.3: Relationship.
SCCIPA will send NK1.2 segment as Lastname^Firstname^MI. Excelicare needs to format these
values correctly to [First NAME][Space][Middle Name][Space][Last Name]
Mandatory Fields:
NK1.2, NK1.3
Example:
NK1|1|DAILEY^MOM^^^^|MO|144 PARKERS CHAPEL RAOD^^PORTLAND^TN^37148ÛSA^^^SUMNER|
(615)491-4187
NK1|2|DAILEY^DAD^^^^|FA|144 PARKERS CHAPEL RAOD^^PORTLAND^TN^37148ÛSA^^^SUMNER|
(615)491-4187
Item
NK1.2
NK1.3
Details
Name
Relationship
Map To
All sub segments concatenated into Contact Name
Default Contact Type to Next of Kin
Table below provides mapping codes to be uses as per
relationship.
Code
Name
CD
CADAVER DONOR
CH
CHILD
CR
CHILD- NO FINC RESP
DM
DEPENDANT OF MINOR
EE
EMPLOYEE
EM
EMPLOYER
FA
FATHER
CF
FOSTER CHILD
GC
GRAND CHILD
GP
GRAND PARENT
HD
HANDICAPPED DEPEND
IJ
INJURED PANTIFF
LP
LIFE PARTNER
MO
MOTHER
NE
NIECE/NEPHEW
OD
ORGON DONOR
OT
OTHER RELATIONSHIP
SA
SELF
SD
SPONSORED DEPEND
SP
SPOUSE
CS
STEP CHILD
SF
STEP FATHER
SM
STEP MOTHER
UN
UNKNOWN
WC
WARD OF COURT
The text here is to be added as the Contact Type
v2.22
p24 of 90

NK1.4
NOK address
NK1.5
NK1.6
Phone
Business Phone
NK1.4.1 address line 1 = Contact Address Line 1

NK1.4.2 address line 2 = Contact Address Line 2
NK1.4.3 city = Contact City
NK1.4.4 State = Contact State
NK1.4.5 Zip = Contact Zip Code
NK1.4.6 Country = Contact Country
NK1.4.7
NK1.4.8
NK1.4.9 County = Contact Address Line 4
Contact - Home Tel
Contact - Work Tel
PV1 Segment Patient Visit

Notes:
This segment will create an entry in the Encounter section of the CCD.
To match PV segment with existing records in Excelicare use PV1.7, PV1.44.
Mandatory Fields:
PV1.7, PV1.10, PV1.44
Example:
QA1A|TEST|DIS|||200810221551|200810230831
ACC|20081022^|11
Item
PV1.2
Details
Patient Status
Map To
Add to Encounter Comment as:
Patient Status = <value>
E - Emergency
I - Inpatient
O - Outpatient
P - Preadmit
PV1.7
Encounter Physician
PV1.9
PV1.10
Primary Care Physician

Hospital Service
Practitioner field on Encounter form

First field: Extract sub-fields and format to [First Name]
[space][Middle Name][space][Last Name][,][Credentials]
Second field: Will be made up of the first three characters
of the surname and the first two characters of the first
name. For example Joe P Benson, MD would be
BENJO
Service admitted to =
PV1.44
PV1.45
Admit Date/Time
Discharge Date/Time
Appendix e HOSPITAL SERVICE provides the list of

code values. Use Dictionary control for this list.
Encounter Eff. Start Date
Encounter Eff. End Date
DG1 Segment Diagnosis

Notes:
This segment will create entries in the problems section of the CCD. To match DG segment with existing
records in Excelicare use DG1.2, DG1.3, DG1.4, and DG1.6
If any of the matching fields are undefined the segment should not be imported and an error should be
v2.22
p25 of 90

raised.
If DG1.2 = l9 then post this value to the CCD, the diagnoses received by the Hospital Interface are
understood to be ICD-9s for encounters. The Excelicare interface will have to be mapped to ICD-9
codes.
Diagnoses that do not have a description should still be imported.
Mandatory Fields:
DG1.2, DG1.3, DG1.4, DG1.6
Example:
DG1|1|I9|786.05|SHORTNESS OF BREATH||A||99|||1406.80|Item#00386||||||N
Item
DG1.2
Details
Code type
DG1.3
DG1.4
DG1.6
Code
Code description
Diagnosis type
Map To
Problem Details Code System. I9 = ICD9 Hardcoded to
this
Problem Details Code
Problem Details Description
Problem Details Comment:
Diagnosis Type = < ADMITTING / WORKING >
MRG Segment Merge - (Do not import)

Notes:
Example:
MRG|||M123456789
Item
MRG.3
Details
Prior Medical Record
Number
Map To
Use this value to find the other side of the merge.
Billing Related Segments

PR1 Segment - Procedures (Do not import)
Notes:
This information is used for the procedures section. To match PR segment with existing records in
Excelicare use PR1.3, PR1.4, and PR1.5.
Example:
PR1|Item#00304|Item#00393|Item#00305|Item#00306|Item#00307|||Item#00311|
Item#00313||Item#00315
Item
PR1.3
Details
Procedure Code
Map To
Procedures Code
Procedures Code System = CPT
PR1.4
PR1.5
Procedure Description
Procedure Date Time
Procedures Description
Procedures Dt/Time
GT1 Segment Guarantor - (Do not import)

Notes:
Example:
GT1|1||DAILEYÂDMIT^^^^||144 PARKERS CHAPEL RAOD^^PORTLAND^TN^37148ÛSA^^^SUMNER
|(615)491-4187||19740926|F||SA|213-45-6547|||HCA - THE HEALTHCARE COMPANY|P.O. B
OX 550^^NASHVILLE^TN^37202-0550|(615)344-9551|||F
Item
Details
Map To
v2.22
p26 of 90

IN1 Segment Insurance (Do not import but note that IN1.2 and IN1.36 are to be used for patient
matching)
Notes:
This information will not be imported to the SCCIPA CCD but the IN1.2 and IN1.36 fields must be read
from the message so that it can be used for patient matching purposes.
Example:
IN1|1|AETNA||AETNA|10 WHITE STREET^ÂNYTOWN^TN^00111ÛSA||6155551212|AETNA GROUP
#|AETNA GROUP NAME|||||||DAILEYÂDMIT^^^^|01|19740926|||||||||||||||||||||||||F
UP||||19740926||F
Item
IN1.2
Details
Insurance plan ID
Map To
Payers Health Payer ID
IN1.4
Insurance Company Name
Payers Payer Name
IN1.5
Insurance Company Address
IN1.7
Insurance Company phone

number
Group Number
Group Name
Plan Effective Date
Plan Expiration Date
Name of Insured
Insureds Relationship to
Patient
IN1.5.1 = address line 1 = Concatenate into Payers

Payer Street
IN1.5.2 = address line 2 = Concatenate into Payers Payer
Street
IN1.5.3 = City = Payers Payer City
IN1.5.4 = State = Payers Payer State
IN1.5.5 = Zip = Payers Payer Zip Code
IN1.5.6 = Country = Payers Payer Country
Payers Payer Phone
IN1.8
IN1.9
IN1.12
IN1.13
IN1.16
IN1.17
IN1.18
IN1.36
Insureds Date of Birth

Policy Number
Payers Group Number

Payers Name
Payers Eff. Start Date
Payers Eff. End Date
Payers Subscriber Name
Payers Patient relationship to subscriber
If Self then set Member ID to be this patients subscriber
ID
If not self then Member ID is left blank
Payers Subscriber DOB
Payers Health Plan Number
ACC Segment Accident - (Do not import)

Notes:
Example:
ACC|20080804^1202|01||MA
Item
Details
Map To
UB1 Segment UB82 Data - (Do not import)

Notes:
Example:
UB1|1||||||03|||||Item#UB1.1
Item
Details
Map To
v2.22
p27 of 90

9
RAD
MSH|^~\&||COCQA1A|||200810131501||ORU^R01|QA1AGTPACS.1.5865|D|2.1
PID|1||J000007420|J7528|TSGRIFFIN^JENI^^^^||19810103|F||||||||||J00008033223
PV1|1|E|J.ER^^||||GRIDE^GRIFFIN^DEBBIE^MPD XXZZXXZZXXZ^^^^^^^^^^^^(615)344-1674|
|||||||||^^^^^^|ER|||||||||||||||||||||COCQA1A||REG
ORC|RE||||S|N|||||||COCQA1A^H
OBR|1|000007607&Y&Y| - Screening Study Bilat Mammo|MAMSB^ - Screening Study Bila
t Mammo^MAMMO|R|200810131350|200810131501|200810131501||||||||GRIDE|(615)344-167
4||||||||P||||||^|||||200810131350
OBX|1|TX|000007607^ - Screening Study Bilat Mammo^MAMSB|1| ~Main QA1A
Name: TSGRIFFIN,JENI~ADDRESS LINE ONE FOR QA1A MAIN
Attending Dr: GRIFFIN,DEBBIE MPD XXZ~ADDRESS LINE TWO FOR QA1A MAIN
DOB: 01/03/1981
Age: 27
Sex: F~ADDRESS LINE THREE FOR QA1A MA
Acct: J00008033223 Loc: J.ER
~Phone #: PHONE 4 QA1A MA
Exam Date: 10/13/2008 Status: REG ER~ Fax #: FAX 4 QA1A MAIN
Radiology No: 000001075~
Unit No:
J000007420~ ~ ~ ~
** Report Has Been Amended **
~ ~
Exams:
Reason for Exam:
CPT CODE:~
000007607 Screening Study Bilat M
76092 ~ ~ ~
Addendum - 10/13/2008 DRAFT (Not yet signed)
~ ~Addendum Status: DRAFT~ADDENDUM: 000007607 MAMMO/MAMSB~ ~This is an addend
a to an existing Report that was done on day it was filed. ~Comparison Film were
reviewed and there has been no changes since the last~exam.~ ~ ~
Reported by: Debbie RR Beason MD~
Dictated Date/Time: 10/13/2008 (
1501)~
Transcribed: 10/13/2008 (1501) 1CSDSG9775~ ~ ~
Report
~Exam: Bilateral Mammogr
aphy.~ ~Reason for Exam: Screening.~ ~Findings: There is no dominant mass. There
are no secondary signs of~malignancy. There are no malignant calcifications. Th
ere is no~significant asymmetry.~ ~Impression: Normal mammograms.~ ~BI-RADS CODE
: 1 - NEGATIVE~FOLLOW-UP CODE: 1Y - NORMAL FOLLOW UP~ ~Note: A negative x-ray re
port should not delay biopsy if otherwise~ ~ ~ ~ ~ ~ ~ ~ ~PAGE 1
S
igned Report
(Continued)~ ~Main QA1A
Att
ending Dr: GRIFFIN,DEBBIE MPD XXZ~ADDRESS LINE TWO FOR QA1A MAIN
DOB
: 01/03/1981
Age: 27
Ac
ct: J00008033223 Loc: J.ER
Exam D
ate: 10/13/2008 Status: REG ER~ Fax #: FAX 4 QA1A MAIN
Radiol
ogy No: 000001075~
Unit No: J000007420
~ ~ ~ ~
~ ~
Exams:
Reason for Exam:
CPT C
ODE:~
76092 ~
<Continued>~ ~clinically indicated. A small percentage of cancers are not
detected~by x-ray.~ ~ ~
** Electronically Signed by DEBBIE GRIFFIN M.D.
**
~
**
on 10/13/2008 at 1451
**
~
Signed by:
DEBBIE GRIFFIN M.D.~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~CC: DR. DEBBIE BEA
SON MD; DEBBIE MPD XXZZXXZZXXZ GRIFFIN~
~Dictated Date/Time: 10/13/2008 (140
8)~Technologist: KEMOYA COOK
~Transcribed Date/Time: 10/13/2008 (1408)~Transcriptionist: 1CSDSG9775/1CSDSG9
775/1CSDSG9775/*~Electronic Signature Date/Time: 10/13/2008 (1451)~Orig Print D/
T: S: 10/13/2008 (1451)~Reprint D/T: 10/13/2008 (1501)
Batch No: N/A
~ ~PA
GE 2
Signed Report
The following table lists all the HL7 (v2.1) Message segments which are potentially used in a
result message.
Segment
MSH
PID
PV1
ORC
OBR
OBX
Description
Message Header
Patient Visit
Common Order
Observation Request
Observation / Result
Frequency
One per Message
One per Message
One per Message
One per Message
One per Message
Multiple per Message
v2.22
p28 of 90

9.1 RAD Process Flow Diagram
The diagrams in section 9.6.1 below describes the processes involved in reading RAD messages
from the queue.
Each RAD message that arrives will have an appropriate ACK sent.
The MSH header will be checked to make sure the right code is in MSH.11 to fit with the
Check MSH9.1 reads ORU to indicate a result message, if something else then error the
message.
Check MSH.3 to make sure this is a RAD message, if not then error the message.
Find PID section and use MRN and URN for Patient Matching against the secondary
identifiers for the hospital from which the message was received.
RAD messages from OConnor hospital will be imported to a hidden Hospital Radiology
OConnor department within the Excelicare Results Reporting module.
RAD messages from St. Louise hospital will be imported to a hidden Hospital Radiology
StLouise department within the Excelicare Results Reporting module.
Note that Radiology results are not intended to be viewed in the Results Reporting module
they are viewed in the Radiology Report section in the CCD.
9.3 Reporting Requirements
Incoming messages for Radiology reports will contain a tilde character to represent the line
break. Radiology reports will require a fixed-width font as there are blank spaces within the
message. Appendix B HL7 Reference for radiology report provides samples for Radiology
Reports for reference.
9.4 ACK
document.
9.5 Segment Details
Notes:
delimiters so for this message
MSH.1 = |
MSH.2 = ^~\&
MSH.3 = blank
etc
Example
Item
MSH.3
MSH.4
Field
Sending Application
Sending Facility
Details
For RAD messages from Good Samaritan, this field will
read HCARad if the message is a radiology result.
For all other hospitals
Assumed to contain the substring RAD, if the incoming
message was received in the RAD drop folder.
For Radiology messages form Good Samaritan/RMCSJ
this will read:
COCQA1A
v2.22
p29 of 90

MSH.7
MSH9.1
MSH.10
Date Time of Message

Message Type
Message Control ID
MSH.11
Processing ID
Map to Date Last Updated.

ORU
copied to the ACK.
the data to:
P = Production
D = Non production

Notes:
Any differences in the demographics will not cause an update to the data within SCCIPA Excelicare.
There will be only one PID per RAD message.
Example:
PID|1||J000001414|J1749|TESTÎNTERFACE^^^^||19750421|F||||||||||J00000021977|123-45-6789
Item
PID.2
PID.3
Details
Map To
Not mapped.
In relation to RAD messages, this field will only be used for
matching. The identifiers in Excelicare will not be updated
for a RAD message.
Note that for OConnor / St. Louise messages it is
essential that the match rule is applied based on the
specific MRN secondary identifier associated with the
source hospital.
PID.4
Medical Record Urn
PID.5
Patient Name
PID.7
PID.8
Patient DOB
Gender
In relation to RAD messages, this field will only be used for

for a RAD message.
OConnor/StLouise URN secondary identifier.
PID.5.1 Last Name
PID.5.2 First Name
PID.5.3 Middle Name
PID.5.4 Suffix
PID.5.5 Title
Patient Gender.
M Male
F Female
U Unknown
PID.9
Patient Alias
Patient other name
v2.22
p30 of 90

PID.10
Race

PID.10.1 code
PID.10.2 Text
PID.10.4 Alt code
PID.10.5 Alt Text
but only PID 10.1 will be used. Code translation as per
table below.
PID.11
Patient Address
Code
Name
A
AI
Asian Indian
B
H
HB
HW
I
M
Multiracial
O
Other
U
Unknown
W
White - Caucasian
PID.11.3 city
PID.11.4 State
PID.11.5 Zip
PID.11.7
PID.11.8
PID.11.9 County
address.
PID.13
PID.14
PID.16
PID.18
PID.19
Patient phone
Marital Status


SSN Number
PID16.1 - Code
Code
Name
D
Divorced
M
Married
S
Single
U
Unknown
W
Widow/Widower
X
Legally Separated
P
Life Partner
v2.22
p31 of 90

Notes:
Example:
PV1|1|I|J.3N^J.190^3|EL|||SEXTON^SEXTON^MELISSA^^^^MD||SEXTON^SEXTON^MELISSA^^^^MD|MED||||CR||Y|
BREME^Brewington^Melissa^^^^MD|IN||TODD||||||||||||||||HOM|||COCQA1A|TEST|DIS|||200810221551|
200810230831
Item
PV1.2
Details
Patient Status
Map To
E - Emergency
I - Inpatient
O - Outpatient
P - Preadmit
PV1.7
Encounter Physician
PV1.9
PV1.10

Hospital Service
Concatenate all sub segments into Encounter

Practitioner
PV1.44
PV1.45
Appendix e HOSPITAL SERVICE provides the list

of code values. Use Dictionary control for this list.
Admit Date/Time
Discharge Date/Time
ORC Segment Common Order Do not import

Notes:
Example:
Item
ORC.5
ORC.13
Details
Order Status
Enterers Location
Map To
This field will allow Excelicare to delete or mark the tests
appropriately.
O ordered
T taken
B bill
C Cancelled = remove data relating to this order
D Draft = Label as Draft
S Signed = Label as final
Exam Facility
Exam Campus
OBR Segment Observation Request

Notes:
Use this segment to build data for the specimen entry. Create if not already recorded or update if already
recorded.
Example:
OBR|1|000007607| - Screening Study Bilat Mammo|MAMSB^ - Screening Study Bilat Mammo^MAMMO|R|
200810131350|200810131501|200810131501||||||||GRIDE|(615)344-1674||||||||P||||||^|||||
200810131350
Item
OBR.2
OBR.3
Details
Placer Order Number
Filler Order Number
Map To
Exam Number
Exam ID
v2.22
p32 of 90

OBR.4
Universal Service ID
OBR4.1 Exam Mnemonic = Radiology Code
OBR4.2 Exam ID as OBR.3 = Radiology Description
OBR4.3 Exam Type Mnemonic
OBR.5
OBR.6
OBR.7
OBR.8
OBR.16
OBR.25
Priority
Requested Date/Time
Observation Date/Time
Observation End Date/Time
Ordering Provider
Result Status
Radiology Code System = Local

Results Reporting add to comment
Results Reporting Authorisation Date
C - Correction to results
If current result is P then error this message as wrong
Result Status
F - Final results; results stored and verified. Can only be
changed with a corrected result.
If current result is C then then error this message as wrong
Result Status.
P - Preliminary: A verified early result is available, final
results not yet obtained.
If current result is flagged F or C then error this message as
wrong Result Status
OBX Segment Observation / Result

Notes:
All OBX segments for a given OBR will be concatenated to make up the complete report.
Example:
OBX|1|TX|000007607^ - Screening Study Bilat Mammo^MAMSB|1| ~Main QA1A
Attending Dr: GRIFFIN,DEBBIE MPD XXZ~ADDRESS LINE TWO FOR QA1A MAIN
DOB: 01/03/1981
Age: 27
Acct: J00008033223 Loc: J.ER
Exam Date: 10/13/2008 Status: REG ER~ Fax #: FAX 4 QA1A MAIN
Radiology No: 000001075~
Unit No:
J000007420~ ~ ~ ~
~ ~
Exams:
Reason for Exam:
CPT CODE:~
76092 ~ ~ ~
Addendum - 10/13/2008 DRAFT (Not yet signed)
~ ~Addendum Status: DRAFT~ADDENDUM: 000007607 MAMMO/MAMSB~ ~This is an addend
a to an existing Report that was done on day it was filed. ~Comparison Film were
reviewed and there has been no changes since the last~exam.~ ~ ~
Dictated Date/Time: 10/13/2008 (
1501)~
Transcribed: 10/13/2008 (1501) 1CSDSG9775~ ~ ~
Report
~Exam: Bilateral Mammogr
aphy.~ ~Reason for Exam: Screening.~ ~Findings: There is no dominant mass. There
are no secondary signs of~malignancy. There are no malignant calcifications. Th
ere is no~significant asymmetry.~ ~Impression: Normal mammograms.~ ~BI-RADS CODE
: 1 - NEGATIVE~FOLLOW-UP CODE: 1Y - NORMAL FOLLOW UP~ ~Note: A negative x-ray re
port should not delay biopsy if otherwise~ ~ ~ ~ ~ ~ ~ ~ ~PAGE 1
S
igned Report
(Continued)~ ~Main QA1A
Att
ending Dr: GRIFFIN,DEBBIE MPD XXZ~ADDRESS LINE TWO FOR QA1A MAIN
DOB
: 01/03/1981
Age: 27
Ac
ct: J00008033223 Loc: J.ER
Exam D
ate: 10/13/2008 Status: REG ER~ Fax #: FAX 4 QA1A MAIN
Radiol
ogy No: 000001075~
Unit No: J000007420
~ ~ ~ ~
~ ~
Exams:
Reason for Exam:
CPT C
ODE:~
76092 ~
<Continued>~ ~clinically indicated. A small percentage of cancers are not
detected~by x-ray.~ ~ ~
** Electronically Signed by DEBBIE GRIFFIN M.D.
**
~
**
on 10/13/2008 at 1451
**
~
Signed by:
DEBBIE GRIFFIN M.D.~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~CC: DR. DEBBIE BEA
SON MD; DEBBIE MPD XXZZXXZZXXZ GRIFFIN~
~Dictated Date/Time: 10/13/2008 (140
v2.22
p33 of 90

8)~Technologist: KEMOYA COOK
~Transcribed Date/Time: 10/13/2008 (1408)~Transcriptionist: 1CSDSG9775/1CSDSG9
775/1CSDSG9775/*~Electronic Signature Date/Time: 10/13/2008 (1451)~Orig Print D/
T: S: 10/13/2008 (1451)~Reprint D/T: 10/13/2008 (1501)
Batch No: N/A
~ ~PA
GE 2
Signed Report
Item
OBX.5
Details
Observation Value
Map To
This is the field that will be concatenated to form the final
report and recorded in the labs module as a radiology
report and in Radiology special form.
~ is newline.
9.6.1 Process RAD HL7 Results to Excelicare

The following flow chart details the process flow of importing Report data into the Excelicare
Labs tables and Radiology Report Special forms.
v2.22
p34 of 90
Figure 5 RAD process Diagram
v2.22
p35 of 90
Figure 6 RAD Process Results to Results Store Diagram
v2.22
p36 of 90

Figure 7 RAD Process Results to CCD Diagram
9.7 RADIOLOGY Report Special form mapping
The Radiology Reports will be added to the Radiology Report Special form once the results have
been imported into the Labs section of Excelicare. Given below are the mapping details to
import data into the Radiology Report Special form.
SEC
TION
DATAITEM
CONTROL
TYPE
CONTROL NAME
Record
Number
Date Last
Updated
Text Box Numeric

Date
Picker Date
Date
Picker
Date
Text Box
Text Box
txtRecordNumber
Combo
Box
cboInvCodeSystem
Default to Local
Text Box
Coding System
Default to Local
Accession
Number
View
Image
Text Box Text Data

Command
Button
txtAccessionNumber
Report
Rich Text
Box
rtbResultReport
OBX.5
Follow rules for all OBX

segments.
Source
Combo
Box
Text Box Text Data
cboSource
Other'
'Other'
txtPersonalProvider
PV1.9
Date of
Exam
Investigat
ion Name
dttDateLastUpdated
RAD
Interface
mapping
Auto
generated
MSH.7
dtDateOfExam
OBR.7
txtInvCode
txtInvestigationName
OBR.4.1
OBR.4.2
Comments
OBR.2.1
cmdViewImage
v2.22
p37 of 90

10
LAB
LAB
MSH|^~\&|LAB|COCQA2|LAB||200811190749||ORU|8410..LAB.QA2|D|2.1
PID|1||I000002918||SYLVAN^PARK^^^^||19700101|M|^^^^^||^^^^|||||||I00000702288
PV1|1|O|I.OA3^^||||UÛNKNOWN^^^^^|||||||||||REF||U|||||||||||||||||||COCQA2||REG|||200810241743
OBR|1|L7172|1119:QAZ:CG00001R^LAB|FAC5^FACTOR V^L|R||200811190740|||P||||200811190740||OA3||1119:QAZ:CG00001R|
1119:QAZ:CG00001R|||200811190749|||FINAL
OBX|1|ST|FAC5^FACTOR V^L|1|100|%|50-150|Normal||AS|FINAL|200811121459|^^^ML^QA2 Main Lab||^|
OBX|2|CE|^^||^^||||||||^^^^||ML^QA2 Main Lab|
OBX|3|AD|2555 Park Plaza||Nashville|TN|37203|||||||||
PID|1||I000003206|I2817|TESTER^GILLY^^^^||19970324|F|^^^^^||^^^^|||||||I00007023904
OBR|1|L7173|1119:QAY:CG00001R^LAB|FAC5^FACTOR V^L|R||200811190754|||JP||||200811190754||OA3||
1119:QAY:CG00001R|1119:QAY:CG00001R|||200811190755|||FINAL
OBX|2|CE|^^||^^||||||||^^^^||ML^QA2 Main Lab|
OBX|3|AD|2555 Park Plaza||Nashville|TN|37203|||||||||
MSH|^~\&|MIC|COCQA2|MIC||200811191031||ORU|8418..LAB.QA2|D|2.1
PID|1||I000003210|I2821|LAB^PARTY^^^^||19650815|M|^^^^^||^^^^|||||U||I00007023942
PV1|1|O|PAML^^|L|||PAML^LAB^PATHOLOGYÂSSOC MEDICAL^^^||||||||||PAML^LAB^PATHOLOGYÂSSOC MEDICAL^^^|REF||
U|||||||||||||||||||COCQA2||REG|||200811191028
OBR|1|M7174|^MIC|GRAMST^GRAM STAIN^L|R||200811191028|||RefClient||||200811191028|URINE^CLEAN CATCH^|PAML||
08:QAY:B0000282R|08:QAY:B0000282R||||||FINAL
OBX|1|ST|GRAMST^GRAM STAIN||See Below||||||FINAL||||^^^^
NTE|1|TX|GRAM STAIN(F)
Coll Date/Time: 11/19/2008 10:28
NTE|2|TX|
Ver Date/Time: 11/19/2008 10:31
NTE|3|TX|SOURCE:
URINE
NTE|4|TX|SPEC DESC: CLEAN CATCH
NTE|5|TX|
NTE|6|TX|EPITHELIAL CELLS
NTE|7|TX|MANY (FLAG: A)
NTE|8|TX|GRAM STAIN
NTE|9|TX|2+ (FLAG: N)
NTE|11|TX|OCCASIONAL
NTE|12|TX|YEAST
OBX|2|CE|||^^||||||||^^^^||ML^QA2 Main Lab
OBX|3|AD|2555 Park Plaza||Nashville|TN|37203
OBR|2|M7174^MIC|^MIC|URINECÛRINE CULTURE^L|R||200811191028|||RefClient||||200811191028|URINE^CLEAN CATCH^|
PAML||08:QAY:B0000282R|08:QAY:B0000282R||||||FINAL
OBX|1|ST|URINECÛRINE CULTURE||See Below||||||FINAL||||^^^^
NTE|1|TX|URINE CULTURE(F)
Coll Date/Time: 11/19/2008 10:28
NTE|2|TX|
Ver Date/Time: 11/19/2008 10:31
NTE|3|TX|SOURCE:
URINE
NTE|5|TX|
NTE|6|TX|
NTE|7|TX|Organism #1 ACINETOBACTER ANITRATUS
OBX|2|CE|||^^||||||||^^^^||ML^QA2 Main Lab
OBX|3|AD|2555 Park Plaza||Nashville|TN|37203
Microbiology
MSH|^~\&|MIC|COCQA1A|MIC||201007201653||ORU|55341..LAB.QA1|D|2.1
PID|1||J000123456|J222222|TEST^PATIENT^^^^||19700101|F|^^^^^|W|8745 TESTING
WAY^^NASHVILLE^TN^37120||(615)888-7777|(615)259-8800||M||J00007654321
PV1|1|I|J.3E^J.3^ZZ|EL|||1CSJAB4456^BURNS^JOYCE^^^^||||||||||1CSJAB4456^BURNS^JOYCE^^^^|IN||
TODD|||||||||||||||||||COCQA1A||ADM|||201007201351
OBR|1|M42800|^MIC|CDIFFT^CLOSTRIDIUM DIFFICILE TOXIN^L|R||201007201300|||GGT||||201007201652|
INTESTINE^^|1CSJAB4456^BURNS^JOYCE^^^^||10:QAX:B0001993R|10:QAX:B0001993R||||||F
OBX|1|ST|CDIFFT^CLOSTRIDIUM DIFFICILE TOXIN||See Below||||||F||^^^ML^QA1 MAIN LAB||^^^ML^QA1 MAIN
LAB
NTE|1||THESE ARE MICRO SPECIMEN COMMENTS
NTE|2|TX|CLOSTRIDIUM DIFFICILE TOXIN(F) Coll Date/Time: 07/20/2010 13:00
NTE|3|TX|
Ver Date/Time: 07/20/2010 16:53
NTE|4|TX|SOURCE:
INTESTINE
NTE|5|TX|SPEC DESC:
NTE|6|TX|
NTE|7|TX|C.DIFFICILE TOXIN
NTE|8|TX|NEGATIVE
OBX|2|CE|||^^||||||||^^^^||ML^QA1 MAIN LAB
OBX|3|AD|2545 Park Plaza|Building 3, 1 West|Nashville|TN|37203
v2.22
p38 of 90

Lab
Segment
MSH
PID
PV1
OBR
NTE
OBX
NTE
Description
Message Header
Patient Visit
Observation request
Notes and Comments
Notes and Comments
Frequency
One per Message
One per Message
One per Message
One or more per Message
Multiple per OBR
Multiple per OBR
Multiple per OBX
Microbiology
Segment
Description
MSH
Message Header
PID
PV1
Patient Visit
OBR
Observation request
NTE
Notes and Comments
OBX
NTE
Notes and Comments
Frequency
One per Message
One per Message
One per Message
One or more per Message
Multiple per OBR
Multiple per OBR
Multiple per OBX
v2.22
p39 of 90

10.2 LAB Process Flow Diagram
Following diagram describes the processes involved in reading PATH messages from the queue;
refer to processing details in section 10.3 for process steps. Steps with an e(number) label, for
example e1, indicate that specific errors may be reported. Steps labelled with a l(number), for
example l1, indicate that messages may be logged to the database. Refer to Appendix d
error description for a full list of errors that may be reported.
Figure 8 LAB Process Flow Diagram
v2.22
p40 of 90

Good Samaritan / HCA data will be loaded to the CCD Lab section under separate departments
such as Hospital Chemistry, Hospital Haematology / Onc, Hospital Microbiology,
Hospital Pathology. A lookup list will be provided of the facilities ordering laboratory services
such as List. Ordering facilities will be incorporated into the CCD, on the lab details screen.
Each LAB message that arrives will have an appropriate ACK sent.
Check MSH.3 reads LAB or MIC to indicate a lab result, if something else then error the
message.
Find PID segment and use for patient matching
o Follow match rules based on PID segments
Use PV segments to create an entry in the encounters section of the CCD
o Create a section if not already recorded
o Update section if record exists for patient.
Check NTE comments
o If NTE is after OBR but before OBX section then comments belong to OBR, store as
specimen comments
o If NTE is after OBX then comments belong to OBX, store as test comments.
Process Segments as detailed below.
LAB messages from OConnor hospital will be imported to the Hospital Labs
MIC messages from OConnor hospital will be imported to the Hospital Microbiology
LAB messages from St. Louise hospital will be imported to the Hospital Labs
MIC messages from St. Louise hospital will be imported to the Hospital Microbiology
10.4 ACK
document.
10.5 Segment Details
Notes:
MSH.1 = |
MSH.2 = ^~\&
MSH.3 = blank
etc.
Example
MSH|^~\&|MIC|COCQA2|MIC||200811191318||ORU|8421..LAB.QA2|D|2.1
Item
Field
Details
v2.22
p41 of 90

MSH.3
Sending Application
MSH.4
Sending Facility
Good Samaritan
Will read HCALab if this is a lab result.
Will read HCAMic if this is a microbiology result.
Assumed to contain the substring LAB, if the incoming
message was received in the Lab drop folder, or MIC, if
the incoming message was received in the Mic drop folder.
MSH.7
MSH.9
MSH.10
Date Time of Message

Message Type
Message Control ID
MSH.11
Processing ID
Map to Date Last Updated.

ORU
copied to the ACK.
the data to:
P = Production
D = Non production

Notes:
There will be only one PID per LAB message.
Example:
123-45-6789
Item
PID.2
PID.3
Details
Map To
Not mapped.
In relation to LAB messages, this field will only be used for
for a LAB message.
source hospital.
PID.4
PID.5
Medical Record Urn
Patient Name
In relation to LAB messages, this field will only be used for

for a LAB message.
PID.5.1 Last Name
PID.5.2 First Name
PID.5.3 Middle Name
PID.5.4 Suffix
PID.5.5 Title
v2.22
p42 of 90

PID.7
PID.8
Patient DOB
Gender

Patient Gender.
M Male
F Female
U Unknown
PID.9
PID.10
Patient Alias
Race
Patient other name

PID.10.1 code
PID.10.2 Text
PID.10.4 Alt code
PID.10.5 Alt Text
table below.
PID.11
Patient Address
Code
Name
A
AI
Asian Indian
B
H
HB
HW
I
M
Multiracial
O
Other
U
Unknown
W
White - Caucasian
PID.11.3 city
PID.11.4 State
PID.11.5 Zip
PID.11.7
PID.11.8
PID.11.9 County
address.
PID.13
PID.14
PID.16
Patient phone
Marital Status

PID16.1 - Code
Code
D
M
S
U
W
X
P
v2.22
Name
Divorced
Married
Single
Unknown
Widow/Widower
Legally Separated
Life Partner
p43 of 90

PID.18
PID.19
SSN Number


Notes:
This segment will create an entry in the Encounter section of the CCD. PV1.44 is not mandatory field
when processing LAB messages.
Example:
Item
PV1.2
Details
Patient Status
PV1.7
PV1.9
PV1.10
Encounter Physician
Hospital Service
Map To
E - Emergency
I - Inpatient
O - Outpatient
P - Preadmit

PV1.44
PV1.45
Admit Date/Time
Discharge Date/Time


Notes:
Use this segment to build data for the specimen entry. Create if not already recorded or update if
already recorded.
Example:
LAB:
OBR|1|L9941|^LAB|CBC^CBC W/AUTO DIFF^L|R||200506161710|||MEDITECH||DC|SOB|
200506161700|MEDITECH|DOEJ^DOE^JANE^M^SR^DR^MD||0616:PAA:H00002R||||
200506161710|||F|Item#00259
MICROBIOLOGY:
OBR|1|M7174|^MIC|GRAMST^GRAM STAIN^L|R||200811191028|||RefClient||||200811191028|URINE^CLEAN
Item
OBR.2
Details
Placer Order Number
Map To
LAB Specimen ID, record in comment if not in field.
OBR2.1 Specimen URN
OBR.4
LAB:
OBR4.1 Order Test Mnemonic. = Short Test Name
OBR4.2 Order Test Name. = Long Test Name
OBR4.3 L to indicate this is a local code.
MIC:
OBR4.1 Result Code or Procedure Mnemonic = Short
Test Name
OBR4.2 Procedure Mnemonic. = Long Test Name
OBR.5
OBR.6
OBR.7
OBR.8
OBR.16
Priority
Requested Date/Time
Ordering Provider
Lab add to comment

Lab add to comment
Lab - Authorisation Date
Lab add to comment
Lab add to comment
v2.22
p44 of 90

OBR.25
Result Status
If current result is P then error this message as wrong
Result Status
F - Final results; results stored and verified. Can only be
changed with a corrected result.
If current result is C then then error this message as wrong
Result Status.
P - Preliminary: A verified early result is available, final
results not yet obtained.
If current result is flagged F or C then error this message
as wrong Result Status

Notes:
All OBX segments for a given OBR will be concatenated to make up the complete report. Each OBX will
NOT be recorded as discreet tests.
Note that all updates to a result are stored within the system. This complete history of change can be
viewed if needed.
For MIC results we will expect the results in the discrete format available.
Example:
Item
OBX.2
Details
Value Type
Map To
ST String (all results will come as ST so we need to do
an Is Numeric check and store what we can as numeric.)
NM Numeric
OBX.5
Observation Value
LAB:
Record content as the result.
MIC:
This will come sent in a textual format.
All OBX and NTE segments should be concatenated in to
the result report.
OBX.6
OBX.7
OBX.8
Units
References Range
Abnormal Flag
Record as the Units used for the test

Record as the reference range for the test
This does not affect the out of range flag we set. The out
of range flag is only set from the data in OBX.8
LAB:
H Above high normal = flag as out of range
HH Above upper panic limits = flag as out of range
L Below low normal = flag as out of range
LL Below lower panic limits = flag as out of range
N Normal
MIC:
R Resistant
I Intermediate
S Susceptible
Record this flag in the comments prefixed with Abnormal
Flag =
v2.22
p45 of 90

Lab = out of range flag is only set using this flag and never
calculated.
OBX.11
Observation Result Status
LAB:
I - Specimen in lab; results pending = Pending
F - Final results; Can only be changed with a corrected
result. = Final
C - Record coming over is a correction and thus replaces
a final result. = Corrected.
MIC:
P - Preliminary results. = Pending
F - Final results; Can only be changed with a corrected
result. = Final
C - Record coming over is a correction and thus replaces
a final result. = Corrected
The status flag must clearly be shown. Record this in the
comment as
Result Status = <word dependent on flag above>
OBX.15
Producers ID
For both LAB and MIC messages

Record at end of Result comment as:
Producer:
OBX.15.1 <newline>
OBX.15.2 <newline>
OBX.15.3 <newline>
OBX.15.4 <newline>
OBX.15.5 <newline>
OBX.15.6 <newline>
OBX.15.7
NTE Segment Notes and Comments

Notes:
If NTE is after OBR but before OBX then comments are for the OBR, store as specimen comments.
If NTE is after OBX then the comments are for the OBX, store as test comments.
Concatenate all NTEs that are together into the same comment.
Example:
NTE|1|TX|GRAM STAIN(F)
NTE|2|TX|
NTE|3|TX|SOURCE:
URINE
NTE|5|TX|
NTE|7|TX|MANY (FLAG: A)
NTE|8|TX|GRAM STAIN
NTE|9|TX|2+ (FLAG: N)
NTE|11|TX|OCCASIONAL
NTE|12|TX|YEAST
Item
NTE.3
Details
Comment
Coll Date/Time: 11/19/2008 10:28

Ver Date/Time: 11/19/2008 10:31
Map To
If occurs after an OBR segment then the notes are
recorded as a comment at the specimen level.
If occurs after an OBX segment then the notes are
recorded as a comment at the test level.
All NTE segments that are grouped together should be
concatenated with a newline after each segment.
v2.22
p46 of 90

Example of NTE Report once concatenated:
GRAM STAIN(F)
Coll Date/Time: 11/19/2008 10:28

Ver Date/Time: 11/19/2008 10:31
SOURCE:
URINE
SPEC DESC: CLEAN CATCH
EPITHELIAL CELLS
MANY (FLAG: A)
GRAM STAIN
2+ (FLAG: N)
EPITHELIAL CELLS
OCCASIONAL
YEAST
v2.22
p47 of 90

11
MDM
MSH|^~\&||COCQA1A|||200810231557||MDM^T04|QA1ADPTO.1.1350|D|2.1|||AL|NE
PID|1||J000106470||DAILEYÂLLIE||20060602|F||W|144 PARKERS CHAPEL ROAD^^PORTLAND^TN^37148||
(615)507-8289|||S|BAP|J00008032017|743-12-5674
PV1|1|I|EPOM-1^P.1^4|EL|||BREME^Brewington^Melissa^^^^MD|||CCU||||CR|||
SEXTON^SEXTON^MELISSA^^^^MD|IN||HMPP|||||||||||||||||||COCQA1A||ADM|||200810080933
TXA||HP^HISTORY AND PHYSICAL EXAM|200810231536|200810231532||200810231532|200810231532||
BREME^Brewington^Melissa^^^^MD||1CSMXB7171^BREWINGTON^MELISSA|J.HIM20081023-0010|||J.HIM|HP|
Signed|||||BREME^Brewington^Melissa^^^^MD^^^^^^^^200810231532
OBX|1|TX|||
OBX|2|TX|||
OBX|3|TX|||
OBX|4|TX|||
OBX|5|TX|||
OBX|6|TX|||
COLUMBIA MEDICAL CENTER HOSPIITAL
OBX|7|TX|||
CENTER CITY, MIDDLE STATE
OBX|8|TX|||
OBX|9|TX|||
OBX|10|TX|||Patient Name:
DAILEY,ALLIE
OBX|11|TX|||Med. Rec. #:
J000106470
OBX|12|TX|||Pt. Acct. #:
J00008032017
OBX|13|TX|||Attnd Phys:
BREME
OBX|14|TX|||Admit Date:
10/08/08
OBX|15|TX|||Birth Date:
06/02/06
OBX|16|TX|||Dictating:
Melissa Brewington, MD
OBX|17|TX|||Physician Add:
OBX|18|TX|||
OBX|19|TX|||
OBX|20|TX|||THIS IS A TEST FOR THE DEPARTMENTAL OUTBOUND TEST INTERFACE SAMPLE FILE. THIS IS A
OBX|21|TX|||TEST FOR THE DEPARTMENTAL OUTBOUND TEST INTERFACE SAMPLE FILE. THIS IS A TEST FOR
OBX|22|TX|||THE DEPARTMENTAL OUTBOUND TEST INTERFACE.
OBX|23|TX|||
OBX|24|TX|||THIS IS A TEST FOR THE DEPARTMENTAL OUTBOUND TEST INTERFACE SAMPLE FILE. THIS IS A
OBX|25|TX|||TEST FOR THE DEPARTMENTAL OUTBOUND TEST INTERFACE SAMPLE FILE. THIS
It is noted, for reference, that the MDM message sent by OConnor / St. Louise can be in either
of two formats (IBEX and MedQuist). It is an assumption in this specification that these MDM
messages will be pre-processed to ensure that only one format is passed through to the MDM
adaptor for OConnor / St. Louise.
This will be the IBEX format which is consistent with the format as sent by Good Samaritan.
v2.22
p48 of 90

11.1 MDM Process Flow Diagram
The following diagram describes the processes involved in reading MDM messages from the
processing queue; refer to processing details in section 11.2 for process steps. Steps with an
e(number) label, for example e1, indicate that specific errors may be reported. Steps labelled
with a l(number), for example l1, indicate that messages may be logged to the database.
Refer to Appendix d error description for a full list of errors that may be reported.
Figure 9 MDM Process Flow Diagram

Each ADT message that arrives will have an appropriate ACK sent.
Check MSH9.1 reads MDM if not then error message
Find PID segment and use for the patient matching
o If one match found then proceed. PID only used for matching not for updating
demographics. Note that the match needs to be performed against the secondary
identifiers corresponding to the source of the message.
v2.22
p49 of 90

All OBX segments will be concatenated and recorded as a document in the references
section of the CCD.
11.3 ACK
document.
Segment
MSH
PID
PV1
TXA
OBX
Description
Message Header
Patient Visit
Transcription Document Header
Frequency
One per message
One per message
One per message
One per message
Multiple per message

Notes:
MSH.1 = |
MSH.2 = ^~\&
MSH.3 = blank
Etc
Example
MSH|^&||J|||200603061441||MDM^T02|PADPTO.1.1|D|2.1|||AL|NE
Item
MSH.4
Field
Sending Facility
Details
MSH.9
Message Type
MSH.10
Message Control ID
MSH.11
Processing ID
MSH9.1 MDM
MSH9.2:
T02 - Original document notification and content.
T04 - Document status change notification and content.
Replace original doc with this one.
T11 - Document cancel notification.
Delete this doc.
copied to the ACK.
the data to:
P = Production
D = Non production

Notes:
v2.22
p50 of 90

There will be only one PID per MDM Message.
Example:
123-45-6789
Item
PID.2
PID.3
Details
Map To
Not mapped.
In relation to MDM messages, this field will only be used
for matching. The identifiers in Excelicare will not be
updated for a MDM message.
source hospital.
PID.4
Medical Record Urn
PID.5
Patient Name
PID.7
PID.8
Patient DOB
Gender
In relation to MDM messages, this field will only be used

updated for a MDM message.
PID.5.1 Last Name
PID.5.2 First Name
PID.5.3 Middle Name
PID.5.4 Suffix
PID.5.5 Title
Patient Gender.
M Male
F Female
U Unknown
PID.9
PID.10
Patient Alias
Race
Patient other name

PID.10.1 code
PID.10.2 Text
PID.10.4 Alt code
PID.10.5 Alt Text
Note Interface should allow for up to six fields in PID
10, but only PID 10.1 will be used. Code translation as
per table below.
Code
A
AI
B
H
HB
HW
I
M
O
Name
Asian Indian
Multiracial
Other
v2.22
p51 of 90
PID.11
Patient Address
U
Unknown
W
White - Caucasian
PID.11.3 city
PID.11.4 State
PID.11.5 Zip
PID.11.7
PID.11.8
PID.11.9 County
address.
PID.13
PID.14
PID.16
PID.18
PID.19
Patient phone
Marital Status


SSN Number
PID16.1 - Code
Code
Name
D
Divorced
M
Married
S
Single
U
Unknown
W
Widow/Widower
X
Legally Separated
P
Life Partner
Patient Identifiers SSN

Notes:
Example:
QA1A|TEST|DIS|||200810221551|200810230831
Item
PV1.2
Details
Patient Status
Map To
E - Emergency
I - Inpatient
O - Outpatient
P - Preadmit
PV1.7
Encounter Physician
PV1.9
PV1.10

Hospital Service
Practitioner field on Encounter form

First field: Extract sub-fields and format to [First Name]
[space][Middle Name][space][Last Name][,][Credentials]
Second field: Will be made up of the first three characters
of the surname and the first two characters of the first
name. For example Joe P Benson, MD would be
BENJO
v2.22
p52 of 90

PV1.44
PV1.45
Admit Date/Time
Discharge Date/Time

TXA Segment Transcription Document Header

Notes:
For a successful MDM segment match with a record in Excelicare use the following TXA2.2: Document
Name and TXA.4: Activity Date
Example:
TXA||HP^History and Physical|Item#TXA.3|Item#TXA.4||200506161635|200506161634||
MAMPR^MAMAKOS^PETER~MAMLA^MAMAKOS^LINDA^R||MEDITECH^Meditech|
CC.HIM20050616-0001||Item#TXA.1|CC.HIM|HP|Draft|||||
MAMPR^MAMAKOS^PETER^^^^^^^^^^^^2007101913|KGM^KGM~MAMPR^MAMPR
Item
TXA.2
Details
Document Type
Map To
TXA.2.1 Mnemonic
TXA.2.2 Description
TXA.4
TXA.8
Activity Date Time

Last Edited Date Time
TXA.9
TXA.17
Originator Code / Name

Document Status
References Date Created

References Comments format as Date Last Modified
<value>
References add to Source Field along with Source
Document Status
TXA.17 Code
Code
DI
DO
IP
IN
PA
AU
LA
Name
Dictated
Documented
In Progress
Incomplete
Pre-Authenticated
Authenticated
Legally Authenticated

Notes:
Concatenate all OBX segments to form the document. Line break between each segment.
All OBX.5 will be concatenated into a PDF report and added to the Supporting Information and
Documentation section of the CCD with margins.
Example:
Item
OBX.5
Details
Observation Value
Map To
This is the field that will be concatenated to form the
document.
v2.22
p53 of 90

12
PATH
v2.22
p54 of 90

MSH|^~\&|NOVOPATH|COCGO|AXSYS EXCELICARE|SCCIPA|201105051608||ORU^R01|GOLABRES.1.6732|P|2.4|||AL
PID|1||M000731234||LASTNAME^FIRSTNAME^MIDDLEINITIAL||19650310|M||||||||||M00346288106
PV1|1|O|M.LAB||||KARRO^Karin^Rom^^^^MD|ZPGSCCIPA^**SCCIPA**|
BORTA^Borodulin^Tatyana^^^^MD|||||||||CLI||||||||||||||||||||||||||201105041026|201105041026
OBR|||GO:CY:11:000429|CYT^CYTOLOGY^L|||201105041139|||||||201105041139||
KARRO^Karin^Rom^^^^MD|||||||||F|||.DNK^Does_Not_Know_PCP~BORTA^Borodulin^Tatyana
OBX|1|TX|
Blank||-------------------------------------------------------------------------------------------||||||FOBX|2|TX|Blank||RUN DATE: 05/05/11
Good Samaritan LAB ***LIVE***
PAGE 1
||||||FOBX|3|TX|Blank||RUN TIME: 1608
Specimen Inquiry
||||||F
OBX|4|TX|Blank||RUN USER: INTERFACE
||||||F
OBX|5|TX|
Blank||-------------------------------------------------------------------------------------------||||||F
OBX|6|TX|Blank||PATIENT: RAMOS,JOHN JOSEPH
ACCT #: M00346288106 LOC: M.LAB
U
#: M000731234||||||F
OBX|7|TX|Blank||
AGE/SX: 46/M
ROOM:
REG: 05/04/11||||||F
OBX|8|TX|Blank||REG DR: Karin,Rom MD
DOB:
03/10/65
BED:
DIS:
||||||F
OBX|9|TX|Blank||
STATUS: DEP CLI
TLOC:
||||||F
OBX|10|TX|
Blank||-------------------------------------------------------------------------------------------||||||F
OBX|11|TX|Blank|| ||||||F
OBX|12|TX|Blank||SPEC #: GO:CY:11:000429
RECD: 05/04/11-1139
STATUS: SOUT
REQ
#: 03495320||||||F
OBX|13|TX|Blank||
COLL: 05/04/11SUBM DR: Karin,Rom MD
||||||F
OBX|15|TX|Blank||ENTERED: 05/04/11-1139
SP TYPE: CYTOLOGY
OTHR DR: Does_Not_Know_PCP
||||||F
OBX|16|TX|Blank||
Borodulin,Tatyana
MD||||||F
OBX|17|TX|Blank||ORDERED: PATH
||||||F
OBX|19|TX|Blank||CODES: P103122 - FNA, PAROTID FINE NEEDLE BIO||||||F
OBX|21|TX|Blank||COPIES TO:||||||F
OBX|22|TX|Blank||
Does_Not_Know_PCP||||||F
OBX|24|TX|Blank||
Borodulin,Tatyana MD||||||F
OBX|25|TX|Blank||
1600 W Campbell Ave Ste 202||||||F
OBX|26|TX|Blank||
Campbell, CA 95008||||||F
OBX|27|TX|Blank||
(408)378-3300||||||F
OBX|29|TX|Blank||
Karin,Rom MD||||||F
OBX|30|TX|Blank||
15861 Winchester Blvd||||||F
OBX|31|TX|Blank||
Los Gatos, CA 95030||||||F
OBX|32|TX|Blank||
(408)395-6121||||||F
OBX|34|TX|Blank||PROCEDURES: PATH (05/04/11-1139)||||||F
OBX|36|TX|Blank||TISSUES: ||||||F
OBX|37|TX|Blank||
FNA, PAROTID - RIGHT||||||F
OBX|39|TX|Blank||
CYTOLOGY GROSS DESCRIPTION||||||F
OBX|41|TX|Blank||
Two smears and one cell block are prepared from 1 cc of brown fluid. ||||||
F
OBX|43|TX|Blank||
CYTOLOGY MICROSCOPIC||||||F
OBX|45|TX|Blank||
The smears and cell block are paucicellular, showing macrophages within
a||||||F
OBX|46|TX|Blank||
background of watery fluid. No epithelium is present for evaluation.
The||||||F
OBX|47|TX|Blank||
findings are those of cyst fluid. There are no clues such as salivary||||||
F
OBX|48|TX|Blank||
gland elements or other epithelium to suggest the nature of this cyst.
||||||F
OBX|50|TX|Blank||
DIAGNOSIS||||||F
OBX|52|TX|Blank||
SALIVARY GLAND, RIGHT PAROTID AREA, FINE NEEDLE ASPIRATION BIOPSY||||||F
v2.22
p55 of 90

OBX|53|TX|Blank||
-- CYST FLUID||||||F
OBX|54|TX|Blank||
||||||F
OBX|55|TX|Blank||
KD/pi
05/05/11 ||||||F
OBX|60|TX|Blank||
** CONTINUED ON NEXT PAGE **||||||F
OBX|62|TX|
Blank||-------------------------------------------------------------------------------------------||||||F
OBX|63|TX|Blank||RUN DATE: 05/05/11
PAGE 2
||||||F
OBX|64|TX|Blank||RUN TIME: 1608
Specimen Inquiry
||||||F
||||||F
OBX|66|TX|
Blank||-------------------------------------------------------------------------------------------||||||F
PATIENT: RAMOS,JOHN JOSEPH
#M00346288106
(Continued)||||||F
OBX|68|TX|
Blank||-------------------------------------------------------------------------------------------||||||F
OBX|71|TX|Blank||
CLINICAL HISTORY||||||F
OBX|73|TX|Blank||
2.5 cm cystic mass in the right tail of parotid area.||||||F
OBX|74|TX|
Blank||-------------------------------------------------------------------------------------------||||||F
OBX|76|TX|Blank||Signed ________________________________
Doeden,Katherine 05/05/11 1607
||||||F
OBX|78|TX|
Blank||-------------------------------------------------------------------------------------------||||||F
v2.22
p56 of 90

OBX|121|TX|Blank||
** END OF REPORT **||||||F
12.1 PATH Process Flow Diagram

Following diagram describes the processes involved in reading PATH messages from the queue;
refer to processing details in section 12.2 for process steps. Steps with an e(number) label, for
example e1, indicate that specific errors may be reported. Steps labelled with a l(number), for
example l1, indicate that messages may be logged to the database. Refer to Appendix d
error description for a full list of errors that may be reported.
Figure 10 PATH Process Flow Diagram

Each PATH (Pathology) message that arrives will have an appropriate ACK sent.
Check MSH.3 reads PATH if not then error message
Find PID segment and use for the patient matching
v2.22
p57 of 90

o If one match found then proceed. PID only used for matching not for updating
demographics. Note that the match must be performed against the appropriate
secondary identifiers according to the source of the message.
PATH messages from OConnor hospital will be imported to the Hospital Pathology
PATH messages from St. Louise hospital will be imported to the Hospital Pathology
All OBX segments will be concatenated and recorded in the references section of the
CCD.
12.3 ACK
document.
Segment
MSH
PID
PV1
TXA
OBX
Description
Message Header
Patient Visit
Transcription Document Header
Frequency
One per message
One per message
One per message
One per message
Multiple per message

Notes:
MSH.1 = |
MSH.2 = ^~\&
MSH.3 = blank
Etc
Example
MSH|^~\&|NOVOPATH|COCGO|AXSYS EXCELICARE|SCCIPA|201105051608||ORU^R01|GOLABRES.1.6732|P|2.4|||AL
Item
MSH.3
MSH.4
Field
Sending Application
Sending Facility
Details
For a message from Good Samaritan this field will read
HCAPath.
Assumed to contain the substring PATH, if the incoming
message was received in the PATH drop folder.
MSH.9
Message Type
MSH9.1 ORU
MSH9.2:
T02 - Original document notification and content.
T04 - Document status change notification and content.
Replace original doc with this one.
T11 - Document cancel notification.
v2.22
p58 of 90

MSH.10
Message Control ID
MSH.11
Processing ID
Delete this doc.

copied to the ACK.
the data to:
P = Production
D = Non production

Notes:
There will be only one PID per PATH message.
Example:
PID|1||M000731234||LASTNAME^FIRSTNAME^MIDDLEINITIAL||19650310|M||||||||||M00346288106
Item
PID.2
PID.3
Details
Map To
Patient Identifiers.
Add as a Source Encounter Number, there will be

multiples of these.
In relation to PATH messages, this field will only be used
updated for a PATH message.
source hospital.
PID.4
Medical Record Urn
PID.5
Patient Name
PID.7
PID.8
Patient DOB
Gender
In relation to PATH messages, this field will only be used

updated for a PATH message.
PID.5.1 Last Name
PID.5.2 First Name
PID.5.3 Middle Name
PID.5.4 Suffix
PID.5.5 Title
Patient Gender.
M Male
F Female
U Unknown
PID.9
PID.10
Patient Alias
Race
Patient other name

PID.10.1 code
PID.10.2 Text
PID.10.4 Alt code
PID.10.5 Alt Text
v2.22
p59 of 90

table below.
Code
A
AI
B
H
HB
Name
Asian Indian
Hispanic African American
Ancestry
HW
I
M
Multiracial
O
Other
U
Unknown
W
White - Caucasian
PID.11.3 city
PID.11.4 State
PID.11.5 Zip
PID.11.7
PID.11.8
PID.11.9 County
PID.11
Patient Address
PID.13
PID.14
PID.16
Patient phone
Marital Status


SSN Number
PID16.1 - Code
Code
Name
D
Divorced
M
Married
S
Single
U
Unknown
W
Widow/Widower
X
Legally Separated
P
Life Partner
Patient Identifiers SSN
PID.18
PID.19

Notes:
Example:
PV1|1|O|M.LAB||||KARRO^Karin^Rom^^^^MD|ZPGSCCIPA^**SCCIPA**|
BORTA^Borodulin^Tatyana^^^^MD|||||||||CLI||||||||||||||||||||||||||201105041026|201105041026
Item
PV1.2
Details
Patient Status
Map To
E - Emergency
I - Inpatient
v2.22
p60 of 90

O - Outpatient
P - Preadmit
PV1.7
PV1.9
PV1.10
Encounter Physician
Hospital Service
Encounter Practitioner
PV1.44
PV1.45
Admit Date/Time
Discharge Date/Time
Appendix e HOSPITAL SERVICE provides the list

of code values. Use Dictionary control for this list.
ORC Segment Common Order

Notes:
Example:
Item
ORC.5
ORC.13
Details
Order Status
Enterers Location
Map To
This field will be allow Excelicare to delete or mark the
tests appropriately.
O ordered
T taken
B bill
C Cancelled = remove data relating to this order
D Draft = Label as Draft
S Signed = Label as final
Exam Facility
Exam Campus

Notes:
Use this segment to build data for the specimen entry. Create if not already recorded or update if
already recorded.
Example:
OBR|||GO:CY:11:000429|CYT^CYTOLOGY^L|||201105041139|||||||201105041139||
KARRO^Karin^Rom^^^^MD|||||||||F|||.DNK^Does_Not_Know_PCP~BORTA^Borodulin^Tatyana
Item
OBR.2
Details
Placer Order Number
Map To
LAB Specimen ID, record in comment if not in
field.
OBR2.1 Specimen URN
OBR.4
LAB:
OBR4.1 Order Test Mnemonic. = Short Test
Name
OBR4.2 Order Test Name. = Long Test Name
MIC:
OBR4.1 Result Code or Procedure Mnemonic =
Short Test Name
OBR4.2 Procedure Mnemonic. = Long Test
Name
OBR.5
Priority
Lab add to comment
v2.22
p61 of 90

OBR.6
Requested Date/Time
OBR.7
OBR.8
OBR.16
Ordering Provider
OBR.25
Result Status
Lab add to comment

Lab - Authorisation Date
Lab add to comment
Lab add to comment
If current result is P then error this message as
wrong Result Status
F - Final results; results stored and verified. Can
only be changed with a corrected result.
If current result is C then then error this message
as wrong Result Status.
P - Preliminary: A verified early result is available,
final results not yet obtained.
If current result is flagged F or C then error this
message as wrong Result Status

Notes:
Concatenate all OBX.5 segments to form the report that is written into Results Reporting. Line break
between each segment.
Example:
OBX|1|TX|
Blank||-------------------------------------------------------------------------------------------||||||F
PAGE 1
||||||F
Specimen Inquiry
||||||F
||||||F
OBX|5|TX|
Blank||-------------------------------------------------------------------------------------------||||||F
OBX|6|TX|Blank||PATIENT: RAMOS,JOHN JOSEPH
ACCT #: M00346288106 LOC: M.LAB
U
#: M000731234||||||F
OBX|7|TX|Blank||
AGE/SX: 46/M
ROOM:
REG: 05/04/11||||||F
OBX|8|TX|Blank||REG DR: Karin,Rom MD
DOB:
03/10/65
BED:
DIS:
||||||F
OBX|9|TX|Blank||
STATUS: DEP CLI
TLOC:
||||||F
OBX|10|TX|
Blank||-------------------------------------------------------------------------------------------||||||F
RECD: 05/04/11-1139
STATUS: SOUT
REQ
#: 03495320||||||F
OBX|13|TX|Blank||
COLL: 05/04/11SUBM DR: Karin,Rom MD
||||||F
OBX|15|TX|Blank||ENTERED: 05/04/11-1139
SP TYPE: CYTOLOGY
OTHR DR: Does_Not_Know_PCP
||||||F
OBX|16|TX|Blank||
Borodulin,Tatyana
MD||||||F
OBX|17|TX|Blank||ORDERED: PATH
||||||F
OBX|19|TX|Blank||CODES: P103122 - FNA, PAROTID FINE NEEDLE BIO||||||F
OBX|21|TX|Blank||COPIES TO:||||||F
OBX|22|TX|Blank||
Does_Not_Know_PCP||||||F
OBX|24|TX|Blank||
Borodulin,Tatyana MD||||||F
OBX|25|TX|Blank||
1600 W Campbell Ave Ste 202||||||F
OBX|26|TX|Blank||
Campbell, CA 95008||||||F
OBX|27|TX|Blank||
(408)378-3300||||||F
OBX|29|TX|Blank||
Karin,Rom MD||||||F
v2.22
p62 of 90

OBX|30|TX|Blank||
15861 Winchester Blvd||||||F
OBX|31|TX|Blank||
Los Gatos, CA 95030||||||F
OBX|32|TX|Blank||
(408)395-6121||||||F
OBX|34|TX|Blank||PROCEDURES: PATH (05/04/11-1139)||||||F
OBX|36|TX|Blank||TISSUES: ||||||F
OBX|37|TX|Blank||
FNA, PAROTID - RIGHT||||||F
OBX|39|TX|Blank||
CYTOLOGY GROSS DESCRIPTION||||||F
OBX|41|TX|Blank||
Two smears and one cell block are prepared from 1 cc of brown fluid. ||||||
F
OBX|43|TX|Blank||
CYTOLOGY MICROSCOPIC||||||F
OBX|45|TX|Blank||
The smears and cell block are paucicellular, showing macrophages within
a||||||F
OBX|46|TX|Blank||
background of watery fluid. No epithelium is present for evaluation.
The||||||F
OBX|47|TX|Blank||
findings are those of cyst fluid. There are no clues such as salivary||||||
F
OBX|48|TX|Blank||
gland elements or other epithelium to suggest the nature of this cyst.
||||||F
OBX|50|TX|Blank||
DIAGNOSIS||||||F
OBX|52|TX|Blank||
SALIVARY GLAND, RIGHT PAROTID AREA, FINE NEEDLE ASPIRATION BIOPSY||||||F
OBX|53|TX|Blank||
-- CYST FLUID||||||F
OBX|54|TX|Blank||
||||||F
OBX|55|TX|Blank||
KD/pi
05/05/11 ||||||F
OBX|60|TX|Blank||
** CONTINUED ON NEXT PAGE **||||||F
OBX|62|TX|
Blank||-------------------------------------------------------------------------------------------||||||F
PAGE 2
||||||F
Specimen Inquiry
||||||F
||||||F
OBX|66|TX|
Blank||-------------------------------------------------------------------------------------------||||||F
PATIENT: RAMOS,JOHN JOSEPH
#M00346288106
(Continued)||||||F
OBX|68|TX|
Blank||-------------------------------------------------------------------------------------------||||||F
OBX|71|TX|Blank||
CLINICAL HISTORY||||||F
OBX|73|TX|Blank||
2.5 cm cystic mass in the right tail of parotid area.||||||F
OBX|74|TX|
Blank||-------------------------------------------------------------------------------------------||||||F
OBX|76|TX|Blank||Signed ________________________________
Doeden,Katherine 05/05/11 1607
||||||F
OBX|78|TX|
Blank||-------------------------------------------------------------------------------------------||||||F
v2.22
p63 of 90

OBX|102|TX|Blank|| ||||||
FOBX|103|TX|Blank|| ||||||F
OBX|121|TX|Blank||
Item
OBX.5
Details
Observation Value
** END OF REPORT **||||||F
Map To
This is the field that will be concatenated to re-constitute
the report.
v2.22
p64 of 90

13
PROCESSING AND TESTING OF MESSAGES

13.1 Expected Volume of Data
The expected volume of data will be as follows; these are based on the average number of
messages currently received by SCCIPA.
Report Type
ADT
LAB
Microbiology
Pathology
Radiology
Reports
Total Reports
Average Number of
messages Received per
day
342
149
28
5
20
60
604
Average number of
messages received per
Week
2394
1043
196
35
140
420
4228
Average number of
messages received per
Year
124830
54385
10220
1825
7300
21900
220460
13.2 Minimum Processing Time

Based on an expected volume of 600 to 1800 records per day, it is requested that the system
be capable of processing in excess of 1800 records in four hours or less. It is noted that the
volume may increase above the upper limit as SCCIPA membership increases and therefore this
interface may need to handle more data than the above estimate.
AxSys shall verify the minimum processing time by testing a batch of 1800 records, comprising
a mix of messages as per the above per day proportions, on the SCCIPA ECProTST
environment.
13.3 Testing Requirements
Hospital results and report data will be searchable using PRISM reporting tools and viewable
within the EMR. Physicians and their staff will be able to view forms for all incoming records
within the patients EMR. If an inappropriately matched record is found then the record will be
inactivated within the EMR.
AxSys will design the interface in such a way that duplicates will not occur if a transaction
record is loaded twice into the AxSys file listener for processing.
For all Laboratory, Microbiology, Pathology, and Radiology incoming messages from Good
Samaritan/HCA, Lab data will have two types of results final and corrected. As results are
processed in real time, the AxSys interface will replace the final results with the ones that have
been corrected, making those corrected results final. Only the most recent results will be
shown.
CCD detail reports from Excelicare will be the same as those currently used by SCCIPA. Lab
detail form contents will hold details for the Laboratory, Microbiology and Pathology results. The
Radiology Details form will hold details for the radiology reports; Appendix B HL7 Reference
for radiology report details sample reports for radiology.
v2.22
p65 of 90

14
ADDITIONAL REQUIREMENTS
As an additional requirement any printouts of the CCD detailed reports will contain the following fields:
Date of Exam
Date of Report
Referred By
Service Provider
Investigation Name
Diagnosis
Provider / Source
Note Font will be a fixed-width font.
v2.22
p66 of 90

15
APPENDIX A ACE SCREENS
v2.22
p67 of 90

NOK
v2.22
p68 of 90
v2.22
p69 of 90
v2.22
p70 of 90
v2.22
p71 of 90

16
APPENDIX B HL7 REFERENCE FOR RADIOLOGY REPORT

16.1 Reports - Discharge Summary HL7 v. 2.3 Sample
MSH|^~\&|NOVORPT|COCGBT|AXSYS EXCELICARE|SCCIPA|201102212145||MDM^T04|
GBTDPTO.1.336950|P|2.3|||AL
PID|1||Q000705939||LASTNAME^LUIS||19740608|M||||||||||Q00846732471|632-22-####
PV1|1|I|Q.2E^Q.202^B||||YEHTZ^Yeh^Tzuoo-Ming^^^^MD|.SELF^SELF|PHAHI^Pham^Hien^^^^MD||||||||
YEHTZ^Yeh^Tzuoo-Ming^^^^MD|IN||||||||||||||||||||||||||201101261625|201101281524
TXA||DS^DISCHARGE SUMMARY REPORT|TX|201102181742||201101261625|||YEHTZ^Yeh^TzuooMing^^^^MD||TRANSTECH^TRANSTECHÛSER|Q.HIM20110219-0194|||Q.HIM|DS|AU|||||
YEHTZ^Yeh^Tzuoo-Ming^^^^MD
OBX|1|TX|Blank|H|------------------------------------------------------------------------------------OBX|2|TX|Blank|H|
REGIONAL MEDICAL CENTER OF SAN JOSE
PATIENT: LASTNAME,LUIS
OBX|3|TX|Blank|H|
SAN JOSE, CALIFORNIA
UNIT: Q000705939
OBX|4|TX|Blank|H|
ACCT#: Q00846732471
OBX|5|TX|Blank|H|
TYPE: DIS IN
OBX|6|TX|Blank|H|------------------------------------------------------------------------------------OBX|7|TX|Blank||DISCHARGE SUMMARY
OBX|8|TX|Blank||
OBX|9|TX|Blank||Tzuoo-Ming Bill Yeh, MD
OBX|10|TX|Blank||
OBX|11|TX|Blank||cc: Hien Pham MD
OBX|12|TX|Blank||
OBX|13|TX|Blank||ADMISSION DATE: 01/26/2011
OBX|14|TX|Blank||
OBX|15|TX|Blank||DISCHARGE DATE: 01/28/2011
OBX|16|TX|Blank||
OBX|17|TX|Blank||FINAL DIAGNOSIS:
OBX|18|TX|Blank||Cholelithiasis with chronic cholecystitis.
OBX|19|TX|Blank||
OBX|20|TX|Blank||OPERATION:
OBX|21|TX|Blank||Laparoscopic cholecystectomy with cholangiography.
OBX|22|TX|Blank||
OBX|23|TX|Blank||BRIEF HISTORY AND PHYSICAL:
OBX|24|TX|Blank||This 36-year-old Hispanic American male was admitted via the emergency room for
OBX|25|TX|Blank||recurrent acute abdominal pain. On admission his temperature was 98.5, pulse
OBX|26|TX|Blank||88, respiratory rate 18, BP 135/80. His lungs were clear. The heart was
OBX|27|TX|Blank||regular. Exam of the abdomen shows mild tenderness over the upper quadrants and
OBX|28|TX|Blank||epigastric area. No evidence of peritoneum signs. No rebound. No masses
OBX|29|TX|Blank||palpable. At discharge his temperature was 97.4, pulse 72, respiratory rate 18,
OBX|30|TX|Blank||BP 118/72. His abdomen was benign. Incision appeared clear and dry.
OBX|31|TX|Blank||
OBX|32|TX|Blank||LABORATORY DATA:
OBX|33|TX|Blank||WBC 5.8. Differential 67% neutrophils, 23% lymphocytes, hemoglobin 14.8,
OBX|34|TX|Blank||hematocrit 42.3. Glucose 90, BUN 10, creatinine 1.1. SGOT 41, SGPT 126,
OBX|35|TX|Blank||alkaline phosphatase 71, total bilirubin 0.6. Ultrasound of the abdomen showed
OBX|36|TX|Blank||multiple small stones in the background of gallbladder sludge and cholesterol
OBX|37|TX|Blank||deposits. The common duct appears normal. Pathology report shows chronic
OBX|38|TX|Blank||cholecystitis with polypoid cholesterolosis.
OBX|39|TX|Blank||
OBX|40|TX|Blank||HOSPITAL COURSE:
OBX|41|TX|Blank||This young man had multiple emergency room visits due to recurrent biliary
OBX|42|TX|Blank||colic. He underwent laparoscopic cholecystectomy with cholangiography on
OBX|43|TX|Blank||01/27/11. He tolerated the procedure well, and his hospital course was
OBX|44|TX|Blank||uneventful. The following day he was ambulatory and taking liquids well.
OBX|45|TX|Blank||
OBX|46|TX|Blank||CONDITION ON DISCHARGE:
OBX|47|TX|Blank||Stable.
OBX|48|TX|Blank||
OBX|49|TX|Blank||DISCHARGE MEDICATIONS:
OBX|50|TX|Blank||Vicodin 1 every 4 hours as needed for pain.
OBX|51|TX|Blank||
OBX|52|TX|Blank||DISPOSITION:
SCCIPA Hospital Interface Specification (SCPA-001) v2.22
p72 of 90

OBX|53|TX|Blank||He was discharged home.
OBX|54|TX|Blank||
OBX|55|TX|Blank||DIET:
OBX|56|TX|Blank||Advance as tolerated.
OBX|57|TX|Blank||
OBX|58|TX|Blank||ACTIVITY:
OBX|59|TX|Blank|X|
OBX|60|TX|Blank|X|
OBX|61|TX|Blank|X|DISCHARGE SUMMARY
LASTNAME,LUIS
OBX|62|TX|Blank|X|
OBX|63|TX|Blank|X|------------------------------------------------------------------------------------OBX|64|TX|Blank|X|
REGIONAL MEDICAL CENTER OF SAN JOSE
PATIENT: LASTNAME,LUIS
OBX|65|TX|Blank|X|
UNIT#: Q000705939
OBX|66|TX|Blank|X|
ACCT#: Q00846732471
OBX|67|TX|Blank|X|------------------------------------------------------------------------------------OBX|68|TX|Blank||As tolerated.
OBX|69|TX|Blank||
OBX|70|TX|Blank||Wound care was instructed. He is to come back to the office for followup.
OBX|71|TX|Blank||
OBX|72|TX|Blank||
OBX|73|TX|Blank||_____________________________
OBX|74|TX|Blank||Tzuoo-Ming Bill Yeh, MD
OBX|75|TX|Blank||
OBX|76|TX|Blank||TY: TRANSTECH D: 02/18/2011 14:42:40 T: 02/19/2011 11:08:23 Document: 581186
OBX|77|TX|Blank|X|
OBX|78|TX|Blank|X|
OBX|79|TX|Blank|X|
OBX|80|TX|Blank|X|
on
at
OBX|81|TX|Blank|X|______________________________________________, ______________
____________
OBX|82|TX|Blank|X|
Yeh,Tzuoo-Ming (Bill) MD
OBX|83|TX|Blank|X|
OBX|84|TX|Blank|X|
OBX|85|TX|Blank|X|
OBX|86|TX|Blank|X|
OBX|87|TX|Blank|X|
OBX|88|TX|Blank|X|Electronically Signed by Tzuoo-Ming (Bill) Yeh, MD on 02/21/11 at 2139
OBX|89|TX|Blank|X|
OBX|90|TX|Blank|X|
OBX|91|TX|Blank|X|
OBX|92|TX|Blank|X|
OBX|93|TX|Blank|X|
OBX|94|TX|Blank|X|
OBX|95|TX|Blank|X|
OBX|96|TX|Blank|X|
OBX|97|TX|Blank|X|
OBX|98|TX|Blank|X|
OBX|99|TX|Blank|X|
OBX|100|TX|Blank|X|
OBX|101|TX|Blank|X|
OBX|102|TX|Blank|X|
OBX|103|TX|Blank|X|
OBX|104|TX|Blank|X|
OBX|105|TX|Blank|X|
OBX|106|TX|Blank|X|
OBX|107|TX|Blank|X|
OBX|108|TX|Blank|X|
OBX|109|TX|Blank|X|
OBX|110|TX|Blank|X|
OBX|111|TX|Blank|X|
OBX|112|TX|Blank|X|
OBX|113|TX|Blank|X|
OBX|114|TX|Blank|X|
OBX|115|TX|Blank|X|
v2.22
p73 of 90

OBX|116|TX|Blank|X|
OBX|117|TX|Blank|X|
OBX|118|TX|Blank|X|
OBX|119|TX|Blank|X|
OBX|120|TX|Blank|X|
OBX|121|TX|Blank|T|
OBX|122|TX|Blank|T|
OBX|123|TX|Blank|T|DISCHARGE SUMMARY
LASTNAME,LUIS
v2.22
p74 of 90

1
Reports - History and Physical HL7 v. 2.3 Sample
MSH|^~\&|NOVORPT|COCGO|AXSYS EXCELICARE|SCCIPA|201102221143||MDM^T04|
GODPTO.1.316181|P|2.3|||AL
PID|1||M000714801||LASTNAME^MARGARET^H||19280413|F||||||||||M00346045683|496-20-####
PV1|1|I|M.3CVP^M.337^4||||KUPSU^Kuppahally^Suman^^^^MD|ZPGSCCIPA^**SCCIPA**|
CONDO^Conlon^Donald^^^^MD||||||||KUPSU^Kuppahally^Suman^^^^MD|INO||||||||||||||||||||||||||201102201836|
201102211412
TXA||HP^HISTORY AND PHYSICAL REPORT|TX|201102202008||201102201836|||
KUPSU^Kuppahally^Suman^^^^MD||TRANSTECH^TRANSTECHÛSER|M.HIM20110220-0377|||M.HIM|HP|
AU|||||KUPSU^Kuppahally^Suman^^^^MD
OBX|1|TX|Blank|H|------------------------------------------------------------------------------------OBX|2|TX|Blank|H|
GOOD SAMARITAN HOSPITAL
OBX|3|TX|Blank|H|
2425 Samaritan Drive
OBX|4|TX|Blank|H|
San Jose, California 95124
OBX|5|TX|Blank|H|
_____________________________________________________________________________________
OBX|6|TX|Blank|X|
OBX|7|TX|Blank|X|HISTORY AND PHYSICAL
OBX|8|TX|Blank|X|
OBX|9|TX|Blank||Suman Kuppahally, MD
OBX|10|TX|Blank||
OBX|11|TX|Blank||
OBX|12|TX|Blank||
OBX|13|TX|Blank||ADMISSION DATE: 02/20/2011
OBX|14|TX|Blank||
OBX|15|TX|Blank||REQUESTING PHYSICIAN:
OBX|16|TX|Blank||ER physician, Dr. Newell.
OBX|17|TX|Blank||
OBX|18|TX|Blank||CHIEF COMPLAINT:
OBX|19|TX|Blank||Presyncope and hypertension.
OBX|20|TX|Blank||
OBX|21|TX|Blank||HISTORY OF PRESENT ILLNESS:
OBX|22|TX|Blank||The patient is an 82-year-old female, a patient of Dr. David Hirschfeld, who
OBX|23|TX|Blank||presented to the emergency room with symptoms of lightheadedness, blurry vision
OBX|24|TX|Blank||and restlessness while standing in the church. Patient had these prodromal
OBX|25|TX|Blank||symptoms and she sat down immediately and did not lose consciousness. Her
OBX|26|TX|Blank||symptoms felt better on sitting down. She had a similar episode several years
OBX|27|TX|Blank||back while standing in the church. She is independent, drives and lives alone
OBX|28|TX|Blank||and has no chest pain, dyspnea on exertion, palpitations, focal weakness,
OBX|29|TX|Blank||headache, or leg edema. No recent illness, fevers, chills, gastrointestinal or
OBX|30|TX|Blank||GU symptoms.
OBX|31|TX|Blank||
OBX|32|TX|Blank||PAST MEDICAL HISTORY:
OBX|33|TX|Blank||Coronary artery disease status post 2-vessel CABG in 2007. At the same time,
OBX|34|TX|Blank||she had mitral valve replacement with a bioprosthetic valve for severe mitral
OBX|35|TX|Blank||regurgitation and mitral valve prolapse, hypertension, hyperlipidemia.
OBX|36|TX|Blank||
OBX|37|TX|Blank||MEDICATIONS:
OBX|38|TX|Blank||Simvastatin 20 daily, lisinopril 20 daily, Coumadin 5 milligrams alternating
OBX|39|TX|Blank||with 6 milligrams daily.
OBX|40|TX|Blank||
OBX|41|TX|Blank||SOCIAL HISTORY:
OBX|42|TX|Blank||No smoking, alcohol or caffeine intake.
OBX|43|TX|Blank||
OBX|44|TX|Blank||FAMILY HISTORY:
OBX|45|TX|Blank||Noncontributory. She is a widow. Her husband passed away 4 years ago.
OBX|46|TX|Blank||
OBX|47|TX|Blank||REVIEW OF SYSTEMS:
OBX|48|TX|Blank||A 10 system review was done which was negative except as noted in HPI.
OBX|49|TX|Blank||
OBX|50|TX|Blank||PHYSICAL EXAMINATION:
OBX|51|TX|Blank||The patient is an elderly female, pleasant, in no acute distress. Vital signs:
OBX|52|TX|Blank||Blood pressure on arrival to the emergency room was 200/94 and she was started
v2.22
p75 of 90

OBX|53|TX|Blank|X|
_____________________________________________________________________________________
OBX|54|TX|Blank|X| GOOD SAMARITAN HOSPITAL
Patient: LASTNAME,MARGARET H
OBX|55|TX|Blank|X| SAN JOSE, CALIFORNIA
Unit #: M000714801
OBX|56|TX|Blank|X|
Acct #: M00346045683
OBX|57|TX|Blank|X| HISTORY AND PHYSICAL REPORT
Type: DIS IN
OBX|58|TX|Blank|X|
Location: M.3CVP
OBX|59|TX|Blank|X|
Room: M.337-4
OBX|60|TX|Blank|X|
OBX|61|TX|Blank|X|------------------------------------------------------------------------------------OBX|62|TX|Blank|X|
GOOD SAMARITAN HOSPITAL
OBX|63|TX|Blank|X|
2425 Samaritan Drive
OBX|64|TX|Blank|X|
San Jose, California 95124
OBX|65|TX|Blank|X|
_____________________________________________________________________________________
OBX|66|TX|Blank|X|
OBX|67|TX|Blank||on nitroglycerin drip and now her blood pressure was 156/91, pulse ranged from
OBX|68|TX|Blank||52 to 66, respiration rate 14, O2 saturation 96% on 2 liters. HEENT: PERRLA,
OBX|69|TX|Blank||EOMI. Neck: Supple, no JVD, no carotid bruits. Lungs: Clear to auscultation
OBX|70|TX|Blank||bilaterally. Abdomen: Soft, nontender. Bowel sounds present. Heart exam:
OBX|71|TX|Blank||Normal S1 and a physiologically split S2 with a louder P2 component, a 3/6
OBX|72|TX|Blank||holosystolic murmur at the apex radiating to the axilla. Extremities: No
OBX|73|TX|Blank||edema, 2+ pulsations. Neuro: Alert and oriented x4, nonfocal exam. Skin: No
OBX|74|TX|Blank||rashes. Musculoskeletal: Benign.
OBX|75|TX|Blank||
OBX|76|TX|Blank||LABORATORY DATA:
OBX|77|TX|Blank||Showed an INR of 2.4. Sodium 139, potassium 4.6, BUN 23, creatinine 1.07.
OBX|78|TX|Blank||Hematocrit 38. CK 120. Troponin less than 0.01. EKG showed normal sinus
OBX|79|TX|Blank||rhythm, no significant ST-T abnormalities. The EKG strip from the paramedics
OBX|80|TX|Blank||showed sinus rhythm with PACs in a bigeminal pattern. The patient had a CT scan
OBX|81|TX|Blank||of the brain in the ER which did not show any acute process, atrophy with small
OBX|82|TX|Blank||vessel disease, no acute intracranial process. Maybe there is an old lacunar
OBX|83|TX|Blank||infarct in the right basal ganglia. Chest x-ray was done which did not show any
OBX|84|TX|Blank||acute cardiopulmonary process.
OBX|85|TX|Blank||
OBX|86|TX|Blank||ASSESSMENT AND PLAN:
OBX|87|TX|Blank||The patient is an 82-year-old female with symptoms of presyncope, most likely
OBX|88|TX|Blank||vasovagal. Valsalva maneuver was tried in the emergency room, which decreased
OBX|89|TX|Blank||her heart rate from 66 to 54 without change in the PR interval and AV
OBX|90|TX|Blank||conduction, and telemetry shows normal rhythm, no arrhythmias or high-grade
OBX|91|TX|Blank||AV block. The patient is bradycardic at baseline and is not on any rate
OBX|92|TX|Blank||lowering medications. For her hypertension, the patient was started on
OBX|93|TX|Blank||nitroglycerin drip and will be titrated up, increase the lisinopril or add a
OBX|94|TX|Blank||dihydropyridine calcium channel blocker. No beta blocker secondary to
OBX|95|TX|Blank||bradycardia. The patient has a bioprosthetic mitral valve and takes Coumadin
OBX|96|TX|Blank||regularly and does not tolerate aspirin. We will continue the medications at
OBX|97|TX|Blank||the same doses. Code status is full code.
OBX|98|TX|Blank||
OBX|99|TX|Blank||
OBX|100|TX|Blank||____________________________
OBX|101|TX|Blank||Suman Kuppahally MD
OBX|102|TX|Blank||
OBX|103|TX|Blank||SK: TRANSTECH D: 02/20/2011 17:08:03 T: 02/20/2011 20:16:56 Document: 583311
OBX|104|TX|Blank|X|
OBX|105|TX|Blank|X|
OBX|106|TX|Blank|X|
OBX|107|TX|Blank|X|
OBX|108|TX|Blank|X|
OBX|109|TX|Blank|X|
OBX|110|TX|Blank|X|Electronically Signed by Suman Kuppahally, MD on 02/22/11 at 1141
OBX|111|TX|Blank|X|
OBX|112|TX|Blank|X|
OBX|113|TX|Blank|T|
_____________________________________________________________________________________
v2.22
p76 of 90

OBX|114|TX|Blank|T| GOOD SAMARITAN HOSPITAL
Patient: LASTNAME,MARGARET H
OBX|115|TX|Blank|T| SAN JOSE, CALIFORNIA
Unit #: M000714801
OBX|116|TX|Blank|T|
Acct #: M00346045683
OBX|117|TX|Blank|T| HISTORY AND PHYSICAL REPORT
Type: DIS IN
OBX|118|TX|Blank|T|
Location: M.3CVP
OBX|119|TX|Blank|T|
Room: M.337-4
v2.22
p77 of 90
17
APPENDIX C HL7 HL7 MESSAGE RESULT SAMPLES

17.1 ADT (Admit, Discharge, Transfer) HL7 v. 2.2 Sample
MSH|^~\&||COCGO|||201102221255||ADTÂ08|GOGTADM.1.10203477|P|2.2
EVN|A08|201102221255|||MHIMCAOÔkumura^CarolÂ
PID|1||M000731557|X27536|LASTNAME^ROBERTÂLEXANDER||19390606|M||W|#### PALMER
DR^^LOS GATOS^CA^95032ÛSA^^^43||(408)378-####|(408)569-####|ENGLISH|S|COCGO|
M00346028891|562-48-####
NK1|1|LASTNAME^MARY|OT|#### PALMER DR^^LOS GATOS^CA^95032ÛSA^^^43|(408)378####|(408)364-####
PV1|1|I|M.3MED^M.315^1|UR|||WANCYN^Wang^Cynthia^^^^MD|ZPGSCCIPA|
WANCYN^Wang^Cynthia^^^^MD|MAS||||PR|AMB||SHENA^Sheth^Nayan^D^^^MD|IN||12||||||||||||||||
HOM|||COCGO|PNA|DIS|||201102142000|201102171425|||||||CHUHE^Chua^Henry^^^^MD
GT1|1||LASTNAME^ROBERTÂ||#### PALMER DR^^LOS GATOS^CA^95032ÛSA^^^43|(408)378####||19390606|M||SA|562-48-####|||ROBERT A LASTNAME|### PALMER DR^^LOS
GATOS^CA^95032|(408)569-####|||S
GT1|2
IN1|1|SCANMCR||SCAN HMO MCR REPLACEMENT|PO BOX 22698^^LONG BEACH^CA^908015698ÛSA||(877)778-7226|0886|SCAN HEALTH PLAN|||20100101||10567388^20110215||
LASTNAME^ROBERTÂ|01|19390606|||||||||||||||||SCCIPA|31076811301|||||||M
ZIN|1|SP|SCAN HMO MCR REPLACEMENT|Y|20110215|AVR/PP/RTM||Y|IN|SCIPA/RTM|||
SCANMCR
17.2 Laboratory Result HL7 v.2.1 Sample
MSH|^~\&|NOVOLAB|COCGO|AXSYS EXCELICARE|SCCIPA|201102220643||ORU^R01|
2713085..LAB.COCGO|P|2.1|||AL
PID|1||M000502971||LASTNAMEÂLDIN||19750708|M||||||||||M00346047156|623-92-####
PV1|1|I|M.MSIC^M.130^1||||LIFJA^Lifshutz^Jason^^^^MD|ZPGSCCIPA^**SCCIPA**|
WARWI^Warshal^William^^^^MD||||||||LIFJA^Lifshutz^Jason^^^^MD|IN||||||||||||||||||||||||||201102210928
OBR|1|L4719234|0222:GO:H00029T|CBC^CBC W/ DIFFERENTIAL^L|T||201102220450|||||||
201102220520||LIFJA^Lifshutz^Jason^^^^MD||||||201102220643|||F
NTE|1||Hold Order Until Specimen Obtained: N
NTE|2||Campus? GSH
OBX|1|ST|NovoInserted^Note||||||||F
NTE|1||Ordering Provider: Jason Lifshutz
OBX|2|ST|WBC^WHITE BLOOD CELL|1|9.0|K/mm3|4.5-11.0||||F||||GO^Good Samaritan
Hospital^2425 Samaritan Drive^^San Jose^CA^95124
OBX|3|ST|RBC^RED BLOOD CELLS|1|4.7|M/mm3|4.6-5.9||||F||||GO^Good Samaritan Hospital^2425
Samaritan Drive^^San Jose^CA^95124
OBX|4|ST|HGB^HEMOGLOBIN|1|14.7|gm/dL|14.0-18.0||||F||||GO^Good Samaritan Hospital^2425
OBX|5|ST|HCT^HEMATOCRIT|1|43|%|42-52||||F||||GO^Good Samaritan Hospital^2425 Samaritan
Drive^^San Jose^CA^95124
OBX|6|ST|MCV^MEAN CELL VOLUME|1|92|fL|80-99||||F||||GO^Good Samaritan Hospital^2425
OBX|7|ST|MCH^MEAN CELL HGB|1|32|pg|27-32||||F||||GO^Good Samaritan Hospital^2425
OBX|8|ST|MCHC^MEAN CELL HGB CONCENTRATION|1|34|g/dL|32-36||||F||||GO^Good Samaritan
OBX|9|ST|RDW^RED CELL DISTRIBUTION WIDTH|1|12.8|%|11.0-16.0||||F||||GO^Good Samaritan
OBX|10|ST|PLT^PLATELET COUNT|1|177|K/mm3|150-350||||F||||GO^Good Samaritan Hospital^2425
OBX|11|ST|NE%^NEUTROPHIL %|1|60|%|50-70||||F||||GO^Good Samaritan Hospital^2425
OBX|12|ST|LY%^LYMPHOCYTE %|1|30|%|20-40||||F||||GO^Good Samaritan Hospital^2425
v2.22
p78 of 90

OBX|13|ST|MO%^MONOCYTE %|1|7|%|0-8||||F||||GO^Good Samaritan Hospital^2425 Samaritan
OBX|14|ST|EO%ÊOSINOPHIL %|1|3|%|0-5||||F||||GO^Good Samaritan Hospital^2425 Samaritan
OBX|15|ST|BA%^BASOPHIL %|1|0|%|0-2||||F||||GO^Good Samaritan Hospital^2425 Samaritan
OBX|16|ST|NovoInsPL^Perfoming Lab:||||||||F
NTE|1||GO - Good Samaritan Hospital 2425 Samaritan Drive San Jose CA 95124
17.3 Microbiology Result HL7 v. 2.1 Sample
MSH|^~\&|NOVOMIC|COCGO|AXSYS EXCELICARE|SCCIPA|201102220727||ORU^R01|
2713314..LAB.COCGO|P|2.1|||AL
PID|1||M000502971||LASTNAMEÂLDIN||19750708|M||||||||||M00346047156|623-92-####
PV1|1|I|M.MSIC^M.130^1||||LIFJA^Lifshutz^Jason^^^^MD|ZPGSCCIPA^**SCCIPA**|
WARWI^Warshal^William^^^^MD||||||||LIFJA^Lifshutz^Jason^^^^MD|IN||||||||||||||||||||||||||201102210928
OBR|1|M4718668|11:GO:M0000503S|CSFC^CSF CULTURE^L|S||201102211230|||||||201102211241|
CEREBRAL SPINAL FLUID|NOOPA^Noone^Patrick^^^^MD|||||||||P
OBX|1|ST|NovoInserted^Note||||||||F
NTE|1||Ordering Provider: Patrick Noone
OBX|2|ST|CSFC^CSF CULTURE||See Below||||||P||||GO^Good Samaritan Hospital^2425 Samaritan
NTE|1||Campus? GSH
NTE|2||Specimen Comment: Culture: TUBE #2
NTE|3|TX|CSF CULTURE(P)
Coll Date/Time: 02/21/2011 12:30
NTE|4|TX|
Ver Date/Time: 02/22/2011 07:27
NTE|5|TX|SOURCE: CEREBRAL SPINAL FLUID
NTE|6|TX|SPEC DESC:
NTE|7|TX
NTE|8|TX|NO GROWTH
NTE|9|TX|NO GROWTH
OBX|3|ST|NovoInsPL^Performing Lab:||||||||F
NTE|1||GO - Good Samaritan Hospital 2425 Samaritan Drive San Jose CA 95124
17.4 Radiology Result HL7 v. 2.1 Sample
MSH|^~\&|NOVORAD|COCGO|AXSYS EXCELICARE|SCCIPA|201102211633||ORU^R01|
GOGTPACS.1.1673482|P|2.1|||AL
PID|1||M000316419||LNAME^JONALYN^MIDDLENAME||19620830|F||||||||||M00346043398
PV1|1|E|M.ED||||CONMI^Congress^Miles^^^^MD|.SELF^SELF|CHIJA^Chien^Jane^^^^MD|||||||||ER
OBR|1|GO001545593| - GD TIBIA FIBULA RT|TIBRT^ - GD TIBIA FIBULA RT^RAD|S||
201102191255|||||||||CONMI|||||||||F|||||||RASH^^201102211632
OBX|1|TX|001545593^ - GD TIBIA FIBULA RT|1|
Patient Name: XXXX,JONALYN
MIDDLENAME~
Unit No: M000316419~ ~ ~ Exams:
CPT:~
001545593 GD TIBIA FIBULA RT
73590~ ~ EXAM: 001545593 - GD TIBIA
FIBULA RT ~
~ DATE: Feb 19, 2011 2:58:00 AM~
~ CLINICAL HISTORY: Right leg pain
down to foot for 2 weeks. ~
~ COMPARISON: None.~
~ FINDINGS: A radiopaque bead
marker is present over the proximal right~ fibula. No underlying bony deformity demonstrated. No
bony fracture~ demonstrated. There is grossly anatomic alignment at visualized joint~ spaces.
Soft tissues are radiographically unremarkable.~
~ IMPRESSION: Unremarkable radiographic
evaluation of the right leg.~
~
~
~
** Electronically Signed by Shannon D Crawford
M.D. **
~
**
on 02/21/2011 at 1632
**
~
Reported and
Signed by: Shannon D Crawford, M.D.~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ CC: Jane W Chien MD~
~
Dictated Date/Time: 02/19/2011 (1255)~ Technologist: Schroeder,Robert A
~
Transcribed Date/Time: 02/19/2011 (1307)~ Transcriptionist: MXOVRADSI/MXOVRADSI~ Orig
Print D/T: S: 02/21/2011 (1633) Batch No: N/A ~ ~ ~ PAGE 1
Signed Report
~ ~ GOOD SAMARITAN HOSPITAL
Name: LNAME,JONALYN MIDDLENAME
~
#### Samaritan Drive
Phys: CONMI - Congress,Miles R MD ~ San Jose, CA 95124
DOB: 08/30/1962 Age: 48
Sex: F~
Acct No: M00346043398 Loc: M.ED
~ Phone #: (408)559-####
Exam Date: 02/19/2011 Status: DEP ER~
Fax #: (408)5592679
Radiology No:
v2.22
p79 of 90

18
APPENDIX D ERROR DESCRIPTION
Refers to error occurred in ADT, RAD, LAB, MDM process diagrams.

Note that where possible the error reported should indicate on which line number of the message the error
was encountered.
Page
Number
/ Error
e1
Cause / Notes
Notify
Message
Next Step
Unable to process message

AxEPPREProcessorHL7
read error.
Yes
(High)
Log error in EP
log, quit process
e2
Unable to process MSH

header wrong type.
Yes
(High)
e3
At least one field for the

lowest level match rule is not
defined in the incoming
message.
Yes
(High)
e4
More than one patient found.
Yes
(High)
e7
Missing NK (Next of Kin)

details.
Yes
(High)
e8
Missing patient visit details
Yes
(High)

header Invalid Code used for
current environment.
segment Invalid Type
used.
Error occurred in PID
segment Entries missing or
Invalid data Patient match
cannot be completed.
Warning More than one
PID segment found, patients
cannot be added.
Warning - NK segment
Invalid or missing
Relationship
Error occurred in PV
segment
e9
Missing diagnosis details
Yes
(High)
Warning GD Segment
Invalid code received
e10
e11
Error caused by malformed

NTE comment
Invalid OBR
Yes
(High)
Yes
(High)
Warning NTE Segment

Missing NTE.3 sub segment.
Error occurred in OBR
segment
e12
Malformed OBX segment
Yes
(High)
e13
Error caused by invalid

document type
Yes
(High)
Error occurred in OBX

segment Missing OBX.5
sub segment Segment
cannot be processed.
Warning TXA Segment Missing Document Type.
e14
Unable to make connection

with Exceliport DB BD
connection error
Yes
(High)
e15
Error caused by malformed

OCR Segment
Yes
(High)
l2
Patient not found, created in

HUB.
Medium
There was an unexpected

error, connection cannot be
made with Exceliport DB +
<EX.MESAGE> +
<DATETIME> +
<Component Name>
Warning - OCR Segment
Warning Patient <Patient
ID> did not exist and was
created on <DATETIME> in
the HUB.
v2.22
Log error in EP
log, quit process
Log error in EP
log, quit process
Log warning in
EP Log and
process.
Log warning in
EP Log and
proceed
Log error in EP
log, quit
process.
Log warning in
EP Log and
proceed
Log in EP Log
and proceed
Log error in EP
log, quit
process.
Log error in EP
log, quit process
Log Warning in
EP log, and
proceed
Log error in EP
log, quit process
Log warning in
EP log and
proceed
Log warning
message to
Exceliport
Database Log
Tables and
Proceed.
p80 of 90

19
APPENDIX E HOSPITAL SERVICE
Code
3 DAY
ACHD
AMB
CARD
CATH
CCU
CR
CT
DCI
DCU
DIAL
DIET
DXTO
ECHO
EEG
EH
EKG
ENDO
ERFT
ERS
FCHD
FNS
GYN
GYNS
HEMO
HOSPICE
ICU
LAB
LBURG
LD
LITH
MAMM
MAMO
MED
MRI
ND
NIC
NM
NSY
NURO
OBANTE
OBED
OBOP
OBOR
OBPP
OBV
OINF
OM
OP
OPROC
OT
PACU
PED
PT
RAD
RADI
REF
Name
3 DAY WINDOW
ANDERSON CO HEALTH DEPT
OUTPATIENT SURGERY
CARDIOLOGY
CATH LAB
CORONARY CARE
CARDIAC REHAB
CAT SCAN
DIALYSIS CLINIC
DIABETIC CARE UNIT
DIALYSIS CLINIC
DIETARY CONSULT
DIAGNOSTIC THERAPUTIC
ECHOCARDIOGRAM
EEG
EMPLOYEE HEALTH
ELECTROCARDIOGRAM
ENDOSCOPIC LAB
EMERGENCY ROOM FAST TRACK
EMERGENCY SERVICES
FRANKLIN CO HEALTH DEPT
FOOD AND NUTRITION SERVICE
GYNECOLOGY
GYNECOLOGY SURGERY
HEMODIALYSIS
HOSPICE
INTENSIVE CARE
LAB SERVICES ONLY
LAWRENCEBURG CLINIC
LABOR AND DELIVERY
LITHOTRIPSY
COCBH
MAMMOGRAPHY
MAMMOGRAPHY
MEDICAL
MRI
EEG/EMG/INVOKED RESPONSE
NEONATAL INTENSIVE CARE
NUCLEAR MEDICINE
NURSERY
NUROLOGY
OBSTETRIC ANTEPARTUM
OBSTETRIC EMERGENCY ROOM
OBSTETRIC OUTPATIENT CLINIC
OBSTETRIC SURGERY
OBSTETRIC POST PARTUM
OBSERVATION/23 HOUR
OUTPATIENT INFUSION THERAPY
OCCUPATIONAL MEDICINE
OUTPATIENT
OUTPATIENT PROCEDURES/SIG/GI
OCCUPATIONAL THERAPY
POST ANESTHESIA CARE
PEDIATRICS
PHYSICAL THERAPY
RADIOLOGY SERVICES
RADIOLOGY SERVICES ONLY
REFERENCE LAB
v2.22
p81 of 90

RP
RESPIRATORY THERAPY
RT
RESPIRATORY THERAPY
SD
STEP DOWN UNIT
SDC
SURGICAL DAY CARE
SL
SLEEP LAB
SLB
SLEEP LAB
SP
SPECIAL PROCEDURES
ST
SPEECH THERAPY
SUR
SURGERY
SURG
SURGERY/GYNECOLOGY
SWG
SWING BED
TELE
TELEMETRY
US
ULTRA SOUND
WCC
WOUND CARE CENTER
ZZZB
MCR PART B CONTINUOUS STAY
v2.22
p82 of 90

20
APPENDIX F COUNTRY CODES
Code
AD
AE
AF
AFGHANISTA
AG
AI
AL
ALBANIA
ALGERIA
AM
AMERICAN S
AN
ANDORA
ANGOLA
ANGUILLA
ANTARCTICA
ANTIGUA/BA
AO
AQ
AR
ARGENTINA
ARMENIA
ARUBA
AS
AT
AU
AUSTRALIA
AUSTRIA
AW
AZ
AZERBAIJAN
BA
BAHAMAS
BAHRAIN
BANGLADESH
BARBADOS
BB
BD
BE
BELARUS
BELGIUM
BELIZE
BENIN
BERMUDA
BF
BG
BH
BHUTAN
BI
BJ
BM
BN
BO
BOLIVIA
BOSNIA/HER
BOTSWANA
BOUVET IS
BR
Name
ANDORRA
UNITED ARAB EMIRATES
AFGHANISTAN
*Afghanistan
ANTIGUA & BARBUDA
ANGUILLA
ALBANIA
*Albania
*Algeria
ARMENIA
*American Samoa
NETHERLANDS ANTILLES
*Andora
*Angola
*Anguilla
*Antarctica
*Antigua and Barbuda
ANGOLA
ANTARCTICA
ARGENTINA
*Argentina
*Armenia
*Aruba
AMERICAN SAMOA
AUSTRIA
AUSTRALIA
*Australia
*Austria
ARUBA
AZERBAIJAN
*Azerbaijan
BOSNIA AND HERZEGOVINA
*Bahamas
*Bahrain
*Bangladesh
*Barbados
BARBADOS
BANGLADESH
BELGIUM
*Belarus
*Belgium
*Belize
*Benin
*Bermuda
BURKINA FASO
BULGARIA
BAHRAIN
*Bhutan
BURUNDI
BENIN
BERMUDA
BRUNEI DARUSSALAM
BOLIVIA
*Bolivia
*Bosnia and Herzegovina
*Botswana
*Bouvet Island
BRAZIL
v2.22
p83 of 90

BRAZIL
BRITISH IN
BRUNEI DAR
BS
BT
BULGARIA
*Brazil
British Indian Ocean Territory
*Brunei Darussalam
BAHAMA
BHUTAN
*Bulgaria
BURKINA FA
BURUNDI
BV
BW
BY
BZ
CA
CAMBODIA
CAMEROON
CANADA
CAPE VERDE
CAYMAN IS
CC
CENTRAL AF
CF
CG
CH
CHAD
CHILE
CHINA
CHRISTMAS
CI
CK
CL
CM
CN
CO
COCOS (KEE
COLUMBIA
COMOROS
CONGO
COOK ISLAN
COSTA RICA
COTE D'IV
CR
CROATIA
CU
CUBA
CV
CX
CY
CYPRUS
CZ
CZECH REPU
CZECHOSLOV
DE
DENMARK
DJ
DJIBOUTI
DK
DM
DO
DOMINICA
DOMINICAN
DZ
*Burkina Faso
*Burundi
BOUVET ISLAND
BOTSWANA
BELARUS
BELIZE
CANADA
*Cambodia
*Cameroon
*Canada
*Cape Verde
*Cayman Islands
COCOS (KEELING) ISLANDS
*Central African Republic
CENTRAL AFRICAN REPUBLIC
CONGO
SWITZERLAND
*Chad
*Chile
*China
*Christmas Island
COTE DIVOIRE (IVORY COAST)
COOK IISLANDS
CHILE
CAMEROON
CHINA
COLOMBIA
*Cocos (Keeling) Islands
*Columbia
*Comoros
*Congo
*Cook Islands
*Costa Rica
*Cote D'Ivoire (Ivory Coast)
COSTA RICA
*Croatia (Hrvatska)
CUBA
*Cuba
CAPE VERDE
CHRISTMAS ISLAND
CYPRUS
*Cyprus
CZECH REPUBLIC
*Czech Republic
*Czechoslovakia (former)
GERMANY
*Denmark
DJIBOUTI
*Djibouti
DENMARK
DOMINICA
DOMINICAN REPUBLIC
*Dominica
*Dominican Republic
ALGERIA
v2.22
p84 of 90

EAST TIMOR
*East Timor
EC
ECUADOR
ECUADOR
*Ecuador
EE
ESTONIA
EG
EGYPT
EGYPT
*Egypt
EH
WESTERN SAHARA
ELSALVADOR
*El Salvador
EQUATORIAL
*Equatorial Guinea
ER
ERITREA
ERITREA
*Eritrea
ES
SPAIN
ESTONIA
*Estonia
ET
ETHIOPIA
ETHIOPIA
*Ethiopia
FALKLAND I
*Falkland Islands (Malvinas)
FAROE ISLA
*Faroe Islands
FI
FINLAND
FIJI
*Fiji
FINLAND
*Finland
FJ
FIJI
FK
FALKLAND ISLANDS (MALVINAS)
FM
MICRONESIA
FO
FAROE ISLANDS
FR
FRANCE
FRANCE
*France
FRANCE MET
*France, Metropolitan
FRENCH GUI
*French Guiana
FRENCH POL
*French Polynesia
FRENCH SOU
*French Southern Territories
FX
FRANCE, METROPOLITAN
GA
GABON
GABON
*Gabon
GAMBIA
*Gambia
GB
UNITED KINGDOM (GREAT BRITAIN)
GD
GRENADA
GE
GEORGIA
GEORGIA
*Georgia
GERMANY
*Germany
GF
FRENCH GUIANA
GH
GHANA
GHANA
*Ghana
GI
GIBRALTAR
GIBRALTAR
*Gibraltar
GL
GREENLAND
GM
GAMBIA
GN
GUINEA
GP
GUADELOUPE
GQ
EQUATORIAL GUINEA
GR
GREECE
GREAT BRIT
*Great Britian (UK)
GREECE
*Greece
GREENLAND
*Greenland
GRENADA
*Grenada
GS
STH GEORGIA/STH SANDWICH ISLND
GT
GUATEMALA
GU
GUAM
GUADELOUPE
*Guadeloupe
GUAM
*Guam
GUATEMALA
*Guatemala
GUINEA
*Guinea
GUINEA-BIS
*Guinea-Bissau
p85 of 90

GUYANA
*Guyana
GW
GUINEA-BISSAU
GY
GUYANA
HAITI
*Haiti
HEARD/MCDO
*Heard and McDonald Islands
HK
HONG KONG
HM
HEARD & MCDONALD ISLANDS
HN
HONDURAS
HONDURAS
*Honduras
HONG KONG
*Hong Kong
HR
CROATIA
HT
HAITI
HU
HUNGARY
HUNGARY
*Hungary
ICELAND
*Iceland
ID
INDONESIA
IE
IRELAND
IL
ISRAEL
IN
INDIA
INDIA
*India
INDONESIA
*Indonesia
IO
BRITISH INDIAN OCEAN TERRITORY
IQ
IRAQ
IR
ISLAMIC REPUBLIC OF IRAN
IRAN
*Iran
IRAQ
*Iraq
IRELAND
*Ireland
IS
ICELAND
ISRAEL
*Israel
IT
ITALY
ITALY
*Italy
JAMAICA
*Jamaica
JAPAN
*Japan
JM
JAMAICA
JO
JORDAN
JORDAN
*Jordan
JP
JAPAN
KAZAKHSTAN
*Kazakhstan
KE
KENYA
KENYA
*Kenya
KG
KYRGYZSTAN
KH
CAMBODIA
KI
KIRIBATI
KIRIBATI
*Kiribati
KM
COMOROS
KN
ST. KITTS AND NEVIS
KOREA NOR
*Korea North
KOREA SOU
*Korea South
KP
KOREA, DEMOCRATIC PEOPLE'S REP
KR
KOREA, REPUBLIC OF
KUWAIT
*Kuwait
KW
KUWAIT
KY
CAYMAN ISLANDS
KYRGYZSTAN
*Kyrgyzstan
KZ
KAZAKHSTAN
LA
LAO PEOPLE'S DEMOCRATIC REPUBL
LAOS
*Laos
LATVIA
*Latvia
LB
LEBANON
LC
SAINT LUCIA
LEBANON
*Lebanon
LESOTHO
*Lesotho
p86 of 90

LI
LIECHTENSTEIN
LIBERIA
*Liberia
LIBYA
*Libya
LIECHTENST
*Liechtenstein
LITHUANIA
*Lithuania
LK
SRI LANKA
LR
LIBERIA
LS
LESOTHO
LT
LITHUANIA
LU
LUXEMBOURG
LUXEMBOURG
*Luxembourg
LV
LATVIA
LY
LIBYAN ARAB JAMAHIRIYA
MA
MOROCCO
MACAU
*Macau
MACEDONIA
*Macedonia
MADAGASCAR
*Madagascar
MALAWI
*Malawi
MALAYSIA
*Malaysia
MALDIVES
*Maldives
MALI
*Mali
MALTA
*Malta
MARSHALL I
*Marshall Islands
MARTINIQUE
*Martinique
MAURITANIA
*Mauritania
MAURITIUS
*Mauritius
MAYOTTE
*Mayotte
MC
MONACO
MD
MOLDOVA, REPUBLIC OF
MEXICO
*Mexico
MG
MADAGASCAR
MH
MARSHALL ISLANDS
MICRONESIA
*Micronesia
ML
MALI
MM
MYANMAR
MN
MONGOLIA
MO
MACAU
MOLDOVA
*Moldova
MONACO
*Monaco
MONGOLIA
*Mongolia
MONTSERRAT
*Montserrat
MOROCCO
*Morocco
MOZAMBIQUE
*Mozambique
MP
NORTHERN MARIANA ISLANDS
MQ
MARTINIQUE
MR
MAURITANIA
MS
MONSERRAT
MT
MALTA
MU
MAURITIUS
MV
MALDIVES
MW
MALAWI
MX
MEXICO
MY
MALAYSIA
MYANMAR
*Myanmar
MZ
MOZAMBIQUE
NA
NAMIBIA
NAMIBIA
*Namibia
NAURU
*Nauru
NC
NEW CALEDONIA
NE
NIGER
NEPAL
*Nepal
NETHER ANT
*Netherlands Antilles
p87 of 90

NETHERLAND
*Netherlands
NEUTRAL ZO
*Neutral Zone
NEW CALEDO
*New Caledonia
NEW ZEALAN
*New Zealand (Aotearoa)
NF
NORFOLK ISLAND
NG
NIGERIA
NI
NICARAGUA
NICARAGUA
*Nicaragua
NIGER
*Niger
NIGERIA
*Nigeria
NIUE
*Niue
NL
NETHERLANDS
NO
NORWAY
NORFOLK IS
*Norfolk Island
NORTHERN M
*Northern Mariana Islands
NORWAY
*Norway
NP
NEPAL
NR
NAURU
NU
NIUE
NZ
NEW ZEALAND
OM
OMAN
OMAN
*Oman
PA
PANAMA
PAKISTAN
*Pakistan
PALAU
*Palau
PANAMA
*Panama
PAPUA NEW
*Papua New Guinea
PARAGUAY
*Paraguay
PE
PERU
PERU
*Peru
PF
FRENCH POLYNESIA
PG
PAPUA NEW GUINEA
PH
PHILIPPINES
PHILIPPINE
*Philippines
PITCAIRN
*Pitcairn
PK
PAKISTAN
PL
POLAND
PM
ST. PIERRE & MIQUELON
PN
PITCAIRN
POLAND
*Poland
PORTUGAL
*Portugal
PR
PUERTO RICO
PT
PORTUGAL
PUERTO RIC
*Puerto Rico
PW
PALAU
PY
PARAGUAY
QA
QATAR
QATAR
*Qatar
RE
RUNION
REUNION
*Reunion
RO
ROMANIA
ROMANIA
*Romania
RU
RUSSIAN FEDERATION
RUSSIAN FE
*Russian Federation
RW
RWANDA
RWANDA
*Rwanda
S GEORGIA
*S Georgia and S Sandwich Isls
SA
SAUDI ARABIA
SAMOA
*Samoa
SAN MARINO
*San Marino
SAO TOME/P
*Sao Tome and Principe
SAUDI ARAB
*Saudi Arabia
p88 of 90

SB
SOLOMON ISLANDS
SC
SEYCHELLES
SD
SUDAN
SE
SWEDEN
SENEGAL
*Senegal
SEYCHELLES
*Seychelles
SG
SINGAPORE
SH
ST. HELENA
SI
SLOVENIA
SIERRA LEO
*Sierra Leone
SINGAPORE
*Singapore
SJ
SVALBARD & JAN MAYEN ISLANDS
SK
SLOVAKIA
SL
SIERRA LEONE
SLOVAK REP
*Slovak Republic
SLOVENIA
*Slovenia
SM
SAN MARINO
SN
SENEGAL
SO
SOMALIA
SOLOMON IS
*Solomon Islands
SOMALIA
*Somalia
SOUTH AFRI
*South Africa
SPAIN
*Spain
SR
SURINAME
SRI LANKA
*Sri Lanka
ST
SAO TOME & PRINCIPE
ST HELENA
*St. Helena
ST KITTS/N
*Saint Kitts and Nevis
ST LUCIA
*Saint Lucia
ST PIERRE
*St. Pierre and Miquelon
ST VINCENT
Saint Vincent & the Grenadines
SUDAN
*Sudan
SURINAME
*Suriname
SV
EL SALVADOR
SVALBARD/J
Svalbard and Jan Mayen Islands
SWAZILAND
*Swaziland
SWEDEN
*Sweden
SWITZERLAN
*Switzerland
SY
SYRIAN ARAB REPUBLIC
SYRIA
*Syria
SZ
SWAZILAND
TAIWAN
*Taiwan
TAJIKSTAN
*Tajikstan
TANZANIA
*Tanzania
TC
TURKS & CAICOS ISLANDS
TD
CHAD
TF
FRENCH SOUTHERN TERRITORIES
TG
TOGO
TH
THAILAND
THAILAND
*Thailand
TJ
TAJIKISTAN
TK
TOKELAU
TM
TURKMENISTAN
TN
TUNISIA
TO
TONGA
TOGO
*Togo
TOKELAU
*Tokelau
TONGA
*Tonga
TP
EAST TIMOR
TR
TURKEY
TRINIDAD/T
*Trinidad and Tobago
TT
TRINIDAD & TOBAGO
p89 of 90

TUNISIA
TURKEY
TURKMENIST
TURKS/CAIC
TUVALU
TV
TW
TZ
UA
UG
UGANDA
UKRAINE
UM
UNITED ARA
UNITED KIN
URUGUAY
US MINOR I
USA
USSR form
UY
UZ
UZBEKISTAN
VA
VANUATU
VATICAN CS
VC
VE
VENEZUELA
VG
VI
VIETNAM
VIRGIN BRI
VIRGIN US
VN
VU
WALLIS/FUT
WESTERN SA
WF
WS
YE
YEMEN
YT
YU
YUGOSLAVIA
ZA
ZAIRE
ZAMBIA
ZIMBABWE
ZM
ZR
ZW
ZZ
*Tunisia
*Turkey
*Turkmenistan
*Turks and Caicos Islands
*Tuvalu
TUVALU
TAIWAN, PROVINCE OF CHINA
TANZANIA, UNITED REPUBLIC OF
UKRAINE
UGANDA
*Uganda
*Ukraine
U.S. MINOR OUTLYING ISLANDS
*United Arab Emirates
*United Kingdom
*Uruguay
*US Minor Outlying Islands
UNITED STATES OF AMERICA
*USSR (former)
URUGUAY
UZBEKISTAN
*Uzbekistan
VATICAN CITY STATE (HOLY SEE)
*Vanuatu
*Vatican City State (Holy See)
ST. VINCENT & THE GRENADINES
VENEZUELA
*Venezuela
BRITISH VIRGIN ISLANDS
UNITED STATES VIRGIN ISLANDS
*Vietnam
*Virgin Islands (British)
*Virgin Islands (U.S.)
VIET NAM
VANUATU
*Wallis and Futuna Islands
*Western Sahara
WALLIS & FUTUNA ISLANDS
SAMOA
YEMEN
*Yemen
MAYOTTE
YUGOSLAVIA
*Yugoslavia
SOUTH AFRICA
*Zaire
*Zambia
*Zimbabwe
ZAMBIA
ZAIRE
ZIMBABWE
UNKNOWN OR UNSPECIFIED COUNTRY
v2.22
p90 of 90

SCCIPA

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

SCCIPA

Încărcat de

Drepturi de autor:

Formate disponibile

AxSys Technology Limited

SCCIPA Hospital Interface Specification

AxSys Project: SCPA-001 (Phase 2)

SCCIPA Hospital Interface Specification

Date Last Modified:

3rd May 2012

Sreedhar T , Brian Heraty, Dean Burton

AxSys Project Team, SCCIPA Team

SCCIPA Hospital Interface Specification (SCPA-001)

AxSys Technology Limited

AxSys Technology Limited

SCCIPA Hospital Interface Specification (SCPA-001)

AxSys Technology Limited

1. DOCUMENT CHANGE CONTROL FORMS

Correction of inaccuracies in spec.

Updated document to introduce

Updated diagram in section 4.3 and

Updates following review with DB

SCCIPA Hospital Interface Specification (SCPA-001)

AxSys Technology Limited

Changes made from: 2.20

Indicate separate queues and queue readers for OConnor /

Update folder paths for drop folders

Updated diagrams to reflect separate queues for OConnor

Updates following review and to reflect discussion with

Changes made from: 2.21

Update to indicate that there is one component for each

Update to include IN1.2 in derivation of the Insurance ID

8.5 (ADT PID),

SCCIPA Hospital Interface Specification (SCPA-001)

AxSys Technology Limited

8.5 (ADT PV1)

Moved description of processing of clinician name from

Remove reference to updating Account Number Patient

10.5 (LAB OBR)

In Notes section, removed sentence referring to HCALab,

11.4 (MDM PV1)

Moved description of processing of clinician name from

11.4 (MDM TXA)

Changed TXA.3 to TXA.8 (the incorrect field reference had

12.4 (PATH OBX)

Clarify that a report is re-constituted from the OBX.5

SCCIPA Hospital Interface Specification (SCPA-001)

AxSys Technology Limited

SCCIPA Hospital Interface Specification (SCPA-001)

AxSys Technology Limited

OVERVIEW AND WORKFLOW OF COMPONENTS

f the initial release of the Hospital Interface

f OConnor/St. Louise Hospital Interface

SCCIPA Hospital Interface Specification (SCPA-001)

AxSys Technology Limited

Mirth channels will be defined to listen to each folder.

This interface is based on the following fundamental assumption:o

SCCIPA Hospital Interface Specification (SCPA-001)

AxSys Technology Limited

3.4 Processing Messages to Backup Directory

3.5 Non-functional Requirements

SCCIPA Hospital Interface Specification (SCPA-001)

AxSys Technology Limited

OConnor/St. Louise Hospital Interface

Source System Vendor

SCCIPA Hospital Interface Specification (SCPA-001)

AxSys Technology Limited