Merge Eye Station™ v. 11.6

1 Merge Eye station v. INTERFACE SPECIFICATIONM erge Healthcare900 Walnut Ridge DriveHartland, WI 53029 Copyright 2017 Merge Healthcare Incorporated, an IBM Company. The content of this document is confidential information of Merge Healthcare Incorporated and its use and disclosure is subject to the terms of the agreement pursuant to which you obtained the software that accompanies the Healthcare is a registered trademark of Merge Healthcare Merge Healthcare logo is a trademark of Merge Healthcare other names are trademarks or registered trademarks of their respective GOVERNMENT RESTRICTED RIGHTS: This product is a Commercial Item offered with Restricted Rights. The Government s rights to use, modify, reproduce, release, perform, display or disclose this documentation are subject to the restrictions set forth in Federal Acquisition Regulation ( FAR ) and for civilian agencies and in DFARS for military agencies.

2 Contractor is Merge FOR USE: Merge Eye station is designed to be used in conjunction with the ophthalmic fundus cameras. As such, the indication for the system is to take images of the : Not for diagnostic use on a mobile device such as a smart phone or a : federal law restricts this device to sale by, or on the order of, a DEVICE IDENTIFIER: Merge EYE STATIONFor application support or to report issues with user documentation, contact Customer Support: Direct Merge Eye station Support: 877-741-5369 Outside of North America: + Email: Web site: latest revision of this document can be found in Merge Sponsor IBM Australia LimitedLevel 13, IBM Centre601 Pacific HighwaySt Leonards, NSW, 2065 AustraliaABN 79 000 024 733 Phone: 1800 117 425 Doc # EUROPEP rinsessegracht 202514 AP, The HagueThe NetherlandsManufacturer s Address Merge Healthcare Incorporated900 Walnut Ridge DriveHartland, WI 530293 Merge EYE station V.

3 HL7 INTERFACE SPECIFICATION purposeMerge Healthcare ConfidentialPurposeThis document is essential in order to evaluate whether an HL7 Information System (IS) can communicate with Eye station . It only describes Segments and Fields that are used by Eye station . Other segments and fields including those required by HL7 standards have been omitted from this and AbbreviationsConventionsTermDescriptionR RequiredOOptionalNNot usedHL7 Health Level 7 IS Information System - the system that Eye station communicates with using HL7 UID Unique Identifier ConventionDescription{ }Curly braces indicate that a segment can repeat[ ]Square brackets indicate that a segment is optional4 Merge EYE station V. HL7 INTERFACE SPECIFICATION contentsMerge Healthcare ConfidentialContentsPurpose.

4 3 Acronyms and Abbreviations .. 3 Conventions .. 3 Contents .. 4 Supported HL7 Messages.. 6 Message Trigger Events.. 6HL7 Message Customization .. 7 Message Rules .. 7 segment definitions .. 7 Message Templates.. 8 Order Messages (ORM) .. 9 MSH segment - Message Header .. 10 PID segment - Patient Identification.. 10PV1 segment - Patient Visit Information .. 11 ORC segment - Common Order .. 11 OBR segment - Observation Request .. 12 Order Result Messages (ORU) .. 12 MSH segment - Message Header .. 13 PID segment - Patient Identification.. 14 ORC segment - Common Order .. 14 OBR segment - Observation Request .. 15 OBX segment .. 16 OBX segment for Order Notification .. 16 OBX segment for Digital Report Notification .. 17 OBX segment for Digital Report Append (Correction).. 18 OBX segment for Interpretation Report Notification .. 18 Medical Document Management (MDM).

5 20 MSH segment - Message Header .. 20 PID segment - Patient Identification.. 21 TXA segment - Patient Identification .. 22 OBX segment .. 225 Merge EYE station V. HL7 INTERFACE SPECIFICATION contentsMerge Healthcare ConfidentialOBX segment for Digital Report Notification .. 22 OBX segment for Digital Report Append (Correction).. 24 OBX segment for Interpretation Report Notification .. 24 Patient Administration Message(ADT) .. 26 MSH segment - Message Header .. 26 PID segment - Patient Identification.. 27 MRG segment - Patient Merge Information .. 28 Staff / Physician Information Message (MFN).. 28 MSH segment - Message Header .. 29 STF segment - Staff Identification .. 29 Acknowledgement Message (ACK) .. 29 MSH segment - Message Header .. 30 MSA segment - Message Acknowledgement .. 31 Query Message (QRY) .. 31 MSH segment - Message Header .. 32 QRD segment - Query Definition.

6 326 Merge EYE station V. HL7 INTERFACE SPECIFICATION supported hl7 messagesMerge Healthcare ConfidentialSupported HL7 MessagesMessage, segment and field definitions used by this interface are based on the HL7 standard and where possible match those specifications. The following messages/events are currently supported by Eye Trigger EventsThe following activities should cause the Information System (IS) to initiate a message: The IS interface sends an order message (ORM) to EyeStation, when an order is created, updated, or cancelled. This message usually contains patient and physician information along with requested observation details. The IS interface sends an ADT message to EyeStation, whenever a patient's demographics are updated, or a patient is merged, or to send a response to demographics query. The IS interface sends an MFN message to EyeStation, whenever a physician information is following activities cause the EyeStation to initiate a message: The EyeStation sends an order result message (ORU) to IS, whenever an order is messageDescriptionOrdersORM^O01 New/update/cancel orderOrder ResultsORU^R01 Result messageDigital ReportsORU^R01 Digital report documentMDM^T02 ORU^R01 Digital report correction/appendix documentMDM^T06 PatientADT^A18 Merge patient/visitADT^A19 Patient query responseADT^A28 Add person informationADT^A31 Update person informationPatient QueryQRY^Q01 Patient demographics queryQBP^Q11 PhysiciansMFN^M02 Add\Update physicianAcknowledgementACKM essage ACK or NACK responseInterpretation ReportsORU^R01 Interpretation report documentMDM^T027 Merge EYE station V.

7 HL7 INTERFACE SPECIFICATION supported hl7 messagesMerge Healthcare Confidential The EyeStation sends an MDM or ORU message to IS, when a digital or interpretation report is created or updated. The EyeStation sends a query message (QRY) to IS, whenever patient validation and additional demographic data is required. The EyeStation sends an ACK message (positive or negative acknowledgement) to IS, when an ORM, ADT, or MFN message is received and Message CustomizationMessage RulesEye station uses message rules to define what segments are included in a particular message type. For example a rule file may contain entries such asMDM^T02:MSH EVN PID PV1 TXA {OBX}ORM^O01:MSH PID ORC OBRORU^R01:MSH PID ORC OBR {OBX}Each incoming and outgoing message must contain only those segments in the given sequence. If incoming messages contain extraneous segments the message will be rejected.

8 It is therefore imperative that Merge implementation personnel configure the message rules to comply with the messages of the connected definitionsEye station also uses segment definition files to define the structure of each segment used in messages and to define the mapping of fields to internal data structures. Eye station fills internal variables from the field location as specified in segment definition file. This means that, for example, FillerOrderNumber could be received in ORC or OBR segment . It is therefore imperative that Merge implementation personnel configure the segment definition files to comply with the message standards of the connected EYE station V. HL7 INTERFACE SPECIFICATION supported hl7 messagesMerge Healthcare ConfidentialA complete list of variables that can be used in segment definitions is given TemplatesEye station generates messages using templates as shown below.

9 It contains all segments, message type and fields that need to be sent with the message. Each %s is a place holder for variables and is replaced with values that are stored in the database. All other fixed fields and constants can also be pre-defined in these |^~\&|Eye station |SCA|HIS|SCA|%s||MDM^T02|%s|D| |AL|AL|PID|||%s||%s||%s|%s|||||||||||||| |||||||||PV1|%s|%s|TXA|1|DS-160|DS|%s||| %s|||||%s|||||AU|patientIdAlternateId1 AlternateId2 AlternateId3 AlternateId4 AlternateId5 AssignAuthForPatientId1 AssignAuthForPatientId2 AssignAuthForPatientId3 AssignAuthForPatientId4 AssignAuthForPatientId5 LastNameFirstNameMiddleNamebirthDatesexR eligionEthnicityAddressStreetAddressOthe rDesignationCityStateOrProvinceZipCodeCo untryHomePhoneNumEmailWorkPhoneNum MessageId MartialNameSuffixMartialFamilyNameBirthN ameSuffixLanguage// Staff FieldsStaffId StaffNameStaffStatusStaffFamilyNameStaff GivenNameStaffMiddlenNameStaffNameSuffix StaffNamePrefixStaffDegreeStaffAssigning AuthorityStaffIdentifierTypeCode// Order

10 FieldsOrderNumberProcedureCodeProcedureN ameAccessionNumberOrderDateTimeOrderingP hysIdOrderingPhysFamilyNameOrderingPhysN ameOrderingPhysGivenNameOrderingPhysMidd lenNameOrderingPhysNameSuffixOrderingPhy sNamePrefixOrderingPhysDegreeOrderingPhy sAssigningAuthorityOrderingPhysIdentifie rTypeCodeInterpretingPhysIdInterpretingP hysFamilyNameInterpretingPhysNameInterpr etingPhysGivenNameInterpretingPhysMiddle nNameInterpretingPhysNameSuffixInterpret ingPhysNamePrefixInterpretingPhysDegreeI nterpretingPhysAssigningAuthorityInterpr etingPhysIdentifierTypeCodePatientAccNum StudyInstanceUIDP atientLocation// Additional Patient fieldsPreviousPatientID9 Merge EYE station V. HL7 INTERFACE SPECIFICATION order messages (orm) Merge Healthcare ConfidentialOrder Messages (ORM)The ORM^O01 message functions as a general order message that is used to transmit information about an trigger event for these messages is any change to an order.