Eclipsys Interfaces   Integration Presentation   Eclipsys   Baroda , India Part I Jan 25 th  2007 Presented by Monisha Ghu...
Introductions
Our Demo Objectives-Session One <ul><li>Introduction and Purpose of HL7 </li></ul><ul><li>Body of an HL7 Message </li></ul...
What are Interfaces? General Definition - “A point of intersection or communication at which independent systems interact”...
Prior to HL7 !!! Where do we start ?
HL7 Background and Information… <ul><li>Health Level Seven is both an American National Standards Institute (ANSI)-accredi...
Introduction and Purpose of Health Level Seven(HL7) <ul><ul><li>HL7 is a standard for information exchange between medical...
HL7 Benefactors … <ul><li>HL7’s endeavors are sponsored, in part, by the support of its benefactors. Few of its benefactor...
International Affiliations   <ul><li>International affiliates have also been established in 26 countries throughout the gl...
Different HL7 Versions <ul><li>HL7 version 2.1 and 2.2 are the older versions of HL7. Both of these versions are used toda...
Different HL7 Versions cont… <ul><li>HL7 Version 2.3 was approved as an ANSI standard  standard in May 1997 developed by S...
Different HL7 Versions cont… <ul><li>HL7 Version 2.3.1 - Approved as an ANSI standard in April 1999.  </li></ul><ul><li>HL...
Different HL7 Versions cont… <ul><li>HL7 Version 2.4   </li></ul><ul><li>HL7 Version 2.4 was approved as an ANSI standard ...
Different HL7 Versions cont… <ul><li>HL7 Version 3.0 </li></ul><ul><li>HL7 Version 3.0 is being refined and is expected to...
Why isn't HL7 Plug and Play? <ul><li>Missing fields - Some vendors tend to omit fields in the message instead of leaving t...
Message Type, Events ,Segments and Fields <ul><li>Message Type </li></ul><ul><li>Each message has a  message type  that de...
Message Type, Events , Segments and Fields cont.. <ul><li>Trigger Events- </li></ul><ul><ul><li>The  Trigger events  are e...
Message Type, Events ,Segments and Fields cont.. <ul><li>Segments </li></ul><ul><li>Messages are comprised of segments. </...
Data Mapping/Translations <ul><li>Importance of Data mappings: </li></ul><ul><li>The purpose of data mapping is to perform...
Data Mapping cont..
Data Mapping cont… <ul><li>In the example below PID-8  “F” is translated to “Female” in SXA(PCS) </li></ul><ul><li>;client...
Defining Applications <ul><ul><li>Define applications in the application dictionary that communicate with Sunrise XA Clini...
Defining Communication Process <ul><li>Define communication processes for the different ancillary applications.  </li></ul...
Defining Communication Process Defined in application dictionary Communication Process
HL7 Example showing the Comm. Process <ul><li>;client,10.138.50.2,8889 Receive from SXA(InterfacesLite does not use this )...
Outbound Configuration (Orders/Tasks) <ul><li>Configuration Tools/Item Catalog/Ordering Info. </li></ul><ul><li>Select app...
Outbound Configuration (Orders/Tasks) Comm. Process attached to the location(transmission policy defined)
HL7 Interfaces Dictionaries (Environment profile) MSH-3 Sending app(Outbound Messages) MSH-5 Receiving app (Inbound Messag...
HL7 Interfaces Dictionaries (Environment profile) cont… MSH-4 Outbound Messages
HL7 Interfaces Dictionaries (Environment profile) cont… MSH-12 Outbound Messages
HL7 Interfaces Dictionaries (Environment profile) cont… Client Id Type “MRN”attached to the facility(Outbound)
Interfaces Express Load File <ul><li>Express load is a fast means of inserting configuration rows into an SXA Clinical Man...
Interface Express Load File Template Message Type Event Type Application Name
Interfaces Log showing HVC Template Error HVC Template Error
HL7 Interfaces testing   <ul><li>HL7 interface testing is part of the overall HL7 interfaces planning process which includ...
Eclipsys-Test Utilities Interfaceslite and HL7Test <ul><li>Interfaceslite: </li></ul><ul><li>The Interfaceslite program al...
Interfaceslite Executable Path
Invoking Interfaceslite <ul><ul><li>To open, double click interfaceslite.exe in the client install folder  ( C:Program Fil...
Using Interfaceslite to test Inbound data to SXA MESSAGE ACKNOWLEGMENT FROM SXA THAT IT RECEIVED THE MESSAGE HL7 message f...
FAQ-Interfaceslite <ul><li>How do I debug existing HL7 message? </li></ul><ul><li>The best resource for debugging an HL7 m...
HL7 Test Utility   <ul><li>Mimics an Integration Engine. </li></ul><ul><li>Tests messages by delivering them through the i...
HL7Test Utility Executable Path <ul><li>HL7Test Utility   is installed as part of the Clinical Manager Interfaces installa...
HL7Test File Format <ul><li>;client, 192.87.14.210, Port Number (Outbound) </li></ul><ul><li>;client, The Server Name, Por...
HL7 Test GUI Outbound Message
Time to grab a bite ..!!!
Upcoming SlideShare
Loading in …5
×

Interfaces Demo Eclipsys Baroda India Part One

1,911 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,911
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
75
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Background -Prior to the first HL7 standard being published, there was absolutely no framework for negotiation when it came to healthcare IT interfaces. Vendors and providers sat down across the table from each other with blank sheets of paper and simply said, &amp;quot;Where do we start?&amp;quot;
  • Background -Prior to the first HL7 standard being published, there was absolutely no framework for negotiation when it came to healthcare IT interfaces. Vendors and providers sat down across the table from each other with blank sheets of paper and simply said, &amp;quot;Where do we start?&amp;quot;
  • - Headquartered in Ann Arbor, MI, Health Level Seven is like most of the other SDOs in that it is a ANSI-The American National Standards Institute (ANSI) coordinates the development and represents the views of the different stakeholders regarding the different standards .This institute provides a platform to these stakeholders to represent their needs and views on a common platform across the globe . This Institute oversees the creation and use of thousands of norms and guidelines that directly impact businesses in nearly every sector. Comprised of Government agencies, Organizations, Companies, Academic and International bodies, and individuals, the American National Standards Institute (ANSI) represents the interests of more than 125,000 companies and 3.5 million professionals OSI level 7 Protocol This means that HL7&apos;s scope is the format and content of the data exchanged between the applications , not how it&apos;s passed between computers or networks. HL7 does not specify how messages will be delivered between the applications. HL7 does, however, correspond to the conceptual definition of an application-to application interface placed in the seventh layer of the OSI model.. OSI model is the networking framework for implementing protocols in seven layers . OSI model exists in all communications - Health Level Seven is both an American National Standards Institute (ANSI)- approved standards developing organization (SDO) and a standard.
  • The HL7 Standard is not a software application. Nor does it make any assumption about the design or architecture of the receiving application system. The scope of HL7 is restricted to the specification of messages between application systems , and the events triggering them. The broad objective is to provide comprehensive standards for the exchange of data among healthcare software applications. Flexibility of hl7 message In order to be as flexible as possible and achieve a consensus , the HL7 committees were forced to define a lot of fields as optional.95% of the fields in hl7 are optional The downside of this decision is that you cannot be certain that particular information will be present in a given message. This is one of the reasons why the same message may vary significantly from vendor to vendor.
  • HL7 activities are supported by its supporters/sponsors
  • HL7 Version-talk about backward compatibility.. The different versions of the hl7 that are used are designed to have backward compatibility which means that the fields are only ever added to the newer versions and not taken away. Eclipsys uses HL7 version 2.3.1, and there are no plans in place for moving to a higher version at this time since none of our applications support newer versions.
  • Represents a significant proportion of in use today. Mostly live interfaces are using this version. There are updates to the OBR segments and ORU message and some additions of a new field to the ORC segment
  • HL7 Version 2.5 was approved as an ANSI standard in June 2003. HL7 version 2.5 again extends HL7 version 2.4 but does not significantly effect HL7 implementations for PMI/ADT, EMPI , Pathology and radiology orders and results as well as medication order management.
  • HL7 Version 3.0 Since 1991, the HL7 organization has been trying to release version 3.0 of the protocol. Version 3.0 of HL7 is a complete redefinition of the HL7 standard to try and overcome some of the issues with the current standard . The new version may come out before end of this decade. This new version will improve messaging by dramatically reducing optionality. It will be much less complicated and less complex and therefore analysts will require less training to get up to speed. From a HL7 planning perspective, despite the fact that it has been through several ballots HL7 version 3 is still really a work in progress.
  • HL7 Standard is not plug and play as every vendor implements the same HL7 messages in slightly different ways. Supporting Different Versions of HL7 Messages – If the other systems you are interfacing with each use different versions of HL7 messages, you must add the version-specific common schemas to your Microsoft Visual Studio® project. Supporting Different Implementations of the Same Version – If the other systems you are interfacing with use the same HL7 version differently , you might need to customize messages and common schemas Adding   New Message Types – Other systems you are interfacing with might require you to add new message types that they use.
  • Each message starts with an MSH segment that is always mandatory (required). When you receive a HL7 message, you parse the MSH first to determine which message it is.
  • -Demonstrate using Interfaceslite using the test data file: IntFDemo.DataMapping.GenderCodeF.to.female.DisplayinSXADay2.HL7
  • Interfaces dictionaries are defined for the interfaces to work..
  • -Demonstrate in SXA by creating a new visit. Demo how a client id type is attached to the facility. Verifying the outbound log on Set B
  • Eclipsys provides a file called HVCTemplate.blk as a sample that the user can use to create their own interface template file . This must be done before Sunrise XA will transmit HL7 messages via the interfaces. The HVCTemplate.blk file contains templates for the following types of messages: • Order message (ORM) • Pharmacy Task completion (RAS) • Admission, Discharge, Transfer (ADT) The user can make changes to this template depending on what their requirements are. You can copy and modify each template to address your enterprise’s needs. The information is used to specify the content of messages sent from Sunrise XA to each ancillary system. After you create the interface template file, you express load it into the database. You will need to work with the Integration Specialist at your site to determine which HL7 messages and event types are supported, and to determine what the ancillary names are . You may want to set the interface template file up initially, and have the Integration Specialist do the final editing. This template is located under the folder EclipsysSunriseClinical Manager Client version Entdata directory.
  • Demo interfaceslite using the test data file ..demo the send buttons and the editing the file and saving it
  • Demo this
  • Interfaces Demo Eclipsys Baroda India Part One

    1. 1. Eclipsys Interfaces Integration Presentation Eclipsys Baroda , India Part I Jan 25 th 2007 Presented by Monisha Ghuman
    2. 2. Introductions
    3. 3. Our Demo Objectives-Session One <ul><li>Introduction and Purpose of HL7 </li></ul><ul><li>Body of an HL7 Message </li></ul><ul><li>Different Hl7 Versions </li></ul><ul><li>Eclipsys Test Utilities- Interfaceslite and HL7 Test </li></ul><ul><li>Using HL7 test to test the communications and interfaces sub systems </li></ul><ul><li>Importance of HL7 Data mapping </li></ul><ul><li>Setting up Dictionary entries, applications and communication processes </li></ul><ul><li>Installing Interfaces and HL7 Connections </li></ul><ul><li>Interfaces Template </li></ul><ul><li>Eclipsys -Interfaces testing Utilities </li></ul>
    4. 4. What are Interfaces? General Definition - “A point of intersection or communication at which independent systems interact” From Healthcare Industry perspective – “A point of intersection or communication at which various ancillaries (ADT, PRX, LAB), HIM or any system involved in Clinical Patient Care and Management interact”. HL7 is used as a standard for communicating between these systems.
    5. 5. Prior to HL7 !!! Where do we start ?
    6. 6. HL7 Background and Information… <ul><li>Health Level Seven is both an American National Standards Institute (ANSI)-accredited standards organization and a standard. </li></ul><ul><li>The HL7 Organization was founded at the University of Pennsylvania in 1987 and is headquartered in Ann Arbor,MI . </li></ul><ul><li>Started with an original committee of 14 people, now numbers nearly 2,400 members including healthcare providers, vendors and consultants. </li></ul><ul><li>HL7 standard does not specify how messages will be delivered between the applications nor how the data is passed between the computers or networks. </li></ul><ul><li>The term ?Level Seven? refers to the conceptual definition of an application-to application interface placed in the seventh layer of the OSI (Open Systems Interconnection ) model of the International Standards Organization (ISO). </li></ul><ul><li>Health Level Seven has been actively working with XML technology . </li></ul>
    7. 7. Introduction and Purpose of Health Level Seven(HL7) <ul><ul><li>HL7 is a standard for information exchange between medical applications. </li></ul></ul><ul><ul><li>HL7 simplifies interfaces between computer applications by standardizing the format and protocol for the exchange of essential set of patient data among health care computer applications. </li></ul></ul><ul><ul><li>HL7 standard is written from the assumption that an event in the real world of healthcare creates the need for data to flow among systems. </li></ul></ul><ul><ul><li>HL7 specifies the way data exchange between applications will be accomplished. It does not specify how applications store or process this data. Usually a TCP/IP connection or FTP file transfers are used to deliver a message. </li></ul></ul><ul><ul><li>HL7 main aim is to establish a common language among medical applications regardless of platform, architecture or programming language. </li></ul></ul><ul><ul><li>Sunrise Clinical manager uses 2.3.1 version of HL7. </li></ul></ul>
    8. 8. HL7 Benefactors … <ul><li>HL7’s endeavors are sponsored, in part, by the support of its benefactors. Few of its benefactors are : </li></ul><ul><ul><li>Booz Allen Hamilton </li></ul></ul><ul><ul><li>IBM </li></ul></ul><ul><ul><li>Intel Corporation </li></ul></ul><ul><ul><li>GE Healthcare Integrated IT Solutions; </li></ul></ul><ul><ul><li>Oracle Corporation </li></ul></ul><ul><ul><li>Quest Diagnostics Inc </li></ul></ul><ul><ul><li>Accenture </li></ul></ul><ul><ul><li>Wyeth Pharmaceuticals </li></ul></ul>
    9. 9. International Affiliations <ul><li>International affiliates have also been established in 26 countries throughout the globe including Argentina, Australia, Brazil, Canada, Croatia, Czech Republic, Denmark, Finland, France, Germany, Greece, India, Ireland, Italy, Japan, Korea, Mexico, The Netherlands, New Zealand, Spain, Sweden, Switzerland, Taiwan, Turkey and the United Kingdom, and Uruguay. </li></ul>
    10. 10. Different HL7 Versions <ul><li>HL7 version 2.1 and 2.2 are the older versions of HL7. Both of these versions are used today by some health applications. </li></ul><ul><li>HL7 Version 2.1 and 2.2 covered the following: </li></ul><ul><ul><li>HL7 Patient Master Index PMI </li></ul></ul><ul><ul><li>HL7 Admissions Discharge and Transfers ADT </li></ul></ul><ul><ul><li>HL7 Radiology orders and results </li></ul></ul><ul><ul><li>HL7 Pathology orders and results </li></ul></ul><ul><ul><li>HL7 Medication prescribing and drug administration </li></ul></ul>
    11. 11. Different HL7 Versions cont… <ul><li>HL7 Version 2.3 was approved as an ANSI standard standard in May 1997 developed by SDO (Standard Development Organization) and introduced: </li></ul><ul><ul><ul><li>HL7 document management messages </li></ul></ul></ul><ul><ul><ul><li>HL7 appointment servicing messages </li></ul></ul></ul><ul><ul><ul><li>HL7 patient referrals messages </li></ul></ul></ul><ul><ul><ul><li>HL7 track patient goals messages </li></ul></ul></ul>
    12. 12. Different HL7 Versions cont… <ul><li>HL7 Version 2.3.1 - Approved as an ANSI standard in April 1999. </li></ul><ul><li>HL7 version 2.3.1 included updates to: </li></ul><ul><ul><li>HL7 Pathology orders and results messages and HL7 Radiology orders and results messages </li></ul></ul><ul><ul><li>HL7 Medication prescribing and drug administration messages </li></ul></ul><ul><ul><li>HL7 Patient Master Index PMI messages. These changes where particularly relevant to HL7 messaging for Enterprise Master Patient Index including the treatment of Multiple Patient Identifiers </li></ul></ul>
    13. 13. Different HL7 Versions cont… <ul><li>HL7 Version 2.4 </li></ul><ul><li>HL7 Version 2.4 was approved as an ANSI standard in October 2000. Extension of 2.3.1 version. </li></ul><ul><li>HL7 Version 2.5 </li></ul><ul><li>HL7 Version 2.5 was approved as an ANSI standard in June 2003. Extension of 2.4 version. </li></ul>
    14. 14. Different HL7 Versions cont… <ul><li>HL7 Version 3.0 </li></ul><ul><li>HL7 Version 3.0 is being refined and is expected to gradually replace HL7 version 2 implementations. </li></ul><ul><li>Significant Australian and international effort is currently focused on HL7 version 3.0. </li></ul><ul><li>HL7 Version 3.0 is a complete redefinition of the HL7 standard to try and overcome some of the issues with the current standard </li></ul><ul><li>Still a work in progress </li></ul>
    15. 15. Why isn't HL7 Plug and Play? <ul><li>Missing fields - Some vendors tend to omit fields in the message instead of leaving them empty. This will change the number of every subsequent field from the start of the message. </li></ul><ul><li>Same data in different fields - Same information may be located in different fields and even in different segments in different HL7 implementations. </li></ul><ul><li>Same data in different formats - Same data may come in different formats. For example, time stamp information should appear as following: 19991231100000.000 but some vendors divide date and time to different sub-fields 19991231^100000.000. </li></ul><ul><li>Different versions - Existence of a number of different versions will allow data exchange only between applications that support same version of HL7. </li></ul><ul><li>Missing values (including mandatory fields) - Although the standard requires only a limited set of values to be present, (95% of the fields are optional), some vendors omit even those with required values. </li></ul>
    16. 16. Message Type, Events ,Segments and Fields <ul><li>Message Type </li></ul><ul><li>Each message has a message type that defines its purpose. </li></ul><ul><ul><ul><ul><li>ADT = patient administration message </li></ul></ul></ul></ul><ul><ul><ul><ul><li>ORU = result message </li></ul></ul></ul></ul><ul><ul><ul><ul><li>ORM = order messages </li></ul></ul></ul></ul><ul><ul><ul><ul><li>MDM = medical document message </li></ul></ul></ul></ul><ul><ul><ul><ul><li>RAS = pharmacy administration </li></ul></ul></ul></ul><ul><ul><ul><ul><li>RDE = pharmacy response </li></ul></ul></ul></ul>
    17. 17. Message Type, Events , Segments and Fields cont.. <ul><li>Trigger Events- </li></ul><ul><ul><li>The Trigger events are events in the real world of healthcare which create a need for data to flow among systems. For e.g. A trigger event a patient is admitted may cause the need for the data about that patient to be sent to a number of other systems. </li></ul></ul><ul><li>-A01-Admit a patient </li></ul><ul><li>-A02-Transfer a patient </li></ul><ul><li>-A03-Discharge a patient </li></ul><ul><li>-A04-Register a patient </li></ul><ul><ul><li>The message type ADT could have the following events- </li></ul></ul><ul><li>Message Type Trigger Events Description </li></ul><ul><li>ADT A01 Admit a patient </li></ul><ul><li>ADT A02 Transfer a patient </li></ul><ul><li>ADT A03 Discharge a patient </li></ul><ul><li>ADT A04 Register a patient </li></ul>
    18. 18. Message Type, Events ,Segments and Fields cont.. <ul><li>Segments </li></ul><ul><li>Messages are comprised of segments. </li></ul><ul><li>Every line in a message is called a 'segment'. </li></ul><ul><li>Segments are the units that comprise a message. </li></ul><ul><li>Each segment is identified by a unique three character code known as the segment ID . </li></ul><ul><li>Each segment has its own semantic purpose .This means that it contains information of a specific type. For example- </li></ul><ul><ul><li>MSH segment contains information about the sender and receiver of the message, type of the message, time stamp etc. </li></ul></ul><ul><ul><li>EVN contains information about event type </li></ul></ul><ul><ul><li>PID contains the demographic information about the patient such as name,id codes, address and so on. </li></ul></ul><ul><ul><li>PV1 contains the information regarding the patient stay in the hospital such as location assigned, referring doctor etc. </li></ul></ul>
    19. 19. Data Mapping/Translations <ul><li>Importance of Data mappings: </li></ul><ul><li>The purpose of data mapping is to perform a check on whether the two systems can communicate and exchange data in a consistent manner. </li></ul><ul><li>Data mapping is a means of matching up events ,segments and fields between systems. ( Refer HL7 Reference Mapping Guide). </li></ul><ul><li>In many cases, mapping is just confirming that field data is OK to be supplied as is. </li></ul><ul><li>Some fields may need to be translated from one system to another. E.g., O = Outpatient or F=Female. </li></ul><ul><li>Interface Mapping worksheets are used to describe needed manipulation / translation. </li></ul><ul><li>Translating the data so that differing values can be sent between SXA Clinical Manager and ancillaries. </li></ul>
    20. 20. Data Mapping cont..
    21. 21. Data Mapping cont… <ul><li>In the example below PID-8 “F” is translated to “Female” in SXA(PCS) </li></ul><ul><li>;client,VCRNTTEST29,7231 </li></ul><ul><li>;client,VCRNTTEST29,7230 </li></ul><ul><li>;HL7ADT </li></ul><ul><li>;pcs </li></ul><ul><li>//A01 </li></ul><ul><li>MSH|^~&|HL7ADT||PCS||2003101910501530||ADT^A01|323922|P|2.3|%seq%| </li></ul><ul><li>EVN|A01|20031018| </li></ul><ul><li>PID|||6668889^^^MRN||monishaGhuman1019^^^||| F |||||(267)978-2678|(610)722-3250|E|STAYSINGLE|&quot;&quot;||443138127|443128128||||||Indian|Q </li></ul><ul><li>PV1||Inpatient|1A^^^NGH|||||||||||||||AcuteCare|9888^^^Visit|||||||||||||||||||||||||20031003115000| </li></ul>
    22. 22. Defining Applications <ul><ul><li>Define applications in the application dictionary that communicate with Sunrise XA Clinical Manager. Identifies applications that can send messages to or receive messages from SXA Clinical Manager. </li></ul></ul>Applications can receive/send messages
    23. 23. Defining Communication Process <ul><li>Define communication processes for the different ancillary applications. </li></ul><ul><li>Define what must be done with data being sent from SXA Clinical Manager to another application. </li></ul><ul><li>Communication Type = Electronic. </li></ul><ul><li>Receiving Application = Value defined in the application dictionary (e.g.ADT,LAB…). </li></ul><ul><li>Connection Name=HL7 Connections (ADT_OUT,LAB_OUT…). </li></ul><ul><li>Coding standard=OBR-4 and OBX-3 as defined in the Ancillary Coding Standard dictionary. </li></ul>
    24. 24. Defining Communication Process Defined in application dictionary Communication Process
    25. 25. HL7 Example showing the Comm. Process <ul><li>;client,10.138.50.2,8889 Receive from SXA(InterfacesLite does not use this ) </li></ul><ul><li>;client,10.138.50.2,8888 Send to SXA (Interfaceslite does not use this) </li></ul><ul><li>;HL7LAB Sending App (MSH-3 Comm. Process Name) </li></ul><ul><li>;PCS Receiving App (MSH-5 Envprofile/HL7Interfaces/CVApplicationName) </li></ul><ul><li>// CommProcess – Test </li></ul><ul><li>MSH|^~&|HL7LAB|Main Hospital|PCS||%date%%time%||ORU^R01|0029|P|2.2|| </li></ul><ul><li>PID |||20030424LAB1 ^^^MRN||Lab^Result^O^^^|Jones|19710101|M|Pat|3|1313 Mockingbird Lane^^Anywhere^ST^99999^USA|USA|(770) 555-1234~(404) 555-12356|(770) 555-1237~(404) 555-1238|Arameic|S|P|555774444|123-45-6789|AZ0000111 |||||||||||||| </li></ul><ul><li>PV1||Inpatient|1EST^100^A^GH||0001|ACUTE^2^2|32556^Bundie^James|MTAN^Tan^Max|WATSON^Waston^Maria|Surgical|TEMP^TEMP||||||0003^Julip^Mint^Dr^PhD|IP|555774444^^^Visit|A||||||||||||||||||VE|CH|H|AA|||200304231000|| </li></ul><ul><li>OBR|||LABCP00003^|0100520^Electrolytes|||200304231000||^|^^^^^^|||||^^^^|32556^Bundie^James|||||||||||&^&^^^^^^|||||||| </li></ul><ul><li>OBX|1|ST|0100270^Sodium Level||147|mEq/L|140-150||||F||||| </li></ul><ul><li>OBX|2|ST|0100280^Potassium Level||4.9|mEq/L|3.7-5.0||||F||||| </li></ul><ul><li>OBX|3|ST|0100284^Chloride||107|mg/dl|95-105|H|||F|||| </li></ul><ul><li>OBX|4|ST|0100282^Carbon Dioxide, Total||30|mEq/L|20-30||||F||||| </li></ul><ul><li>OBX|5|ST|0100286^Anion Gap||10||||||F|||| </li></ul>MSH-3 Sending Application-Communication Process MSH-5 Receiving Application
    26. 26. Outbound Configuration (Orders/Tasks) <ul><li>Configuration Tools/Item Catalog/Ordering Info. </li></ul><ul><li>Select appropriate Transmission policy, Disc Transmission policy. </li></ul><ul><li>Select appropriate Ancillary Info. </li></ul><ul><li>Configuration Tools/Dictionary/Catalog Information/Transmission policy. </li></ul><ul><li>Configure Transmission policy for patients location/Priority and Communication Process. </li></ul><ul><li>Configuration Tools/Dictionary/Catalog Information/Communication Process. </li></ul><ul><li>Configure Communication Process (specifying Communication Type, Receiving application , Connection name). </li></ul>
    27. 27. Outbound Configuration (Orders/Tasks) Comm. Process attached to the location(transmission policy defined)
    28. 28. HL7 Interfaces Dictionaries (Environment profile) MSH-3 Sending app(Outbound Messages) MSH-5 Receiving app (Inbound Messages)/
    29. 29. HL7 Interfaces Dictionaries (Environment profile) cont… MSH-4 Outbound Messages
    30. 30. HL7 Interfaces Dictionaries (Environment profile) cont… MSH-12 Outbound Messages
    31. 31. HL7 Interfaces Dictionaries (Environment profile) cont… Client Id Type “MRN”attached to the facility(Outbound)
    32. 32. Interfaces Express Load File <ul><li>Express load is a fast means of inserting configuration rows into an SXA Clinical Manager database. </li></ul><ul><li>HVCTemplate.blk used to define what outbound messages SXA Clinical Manager is to send. </li></ul><ul><li>Outbound messages can include orders message(ORM), Pharmacy Task completion (RAS) and patient updates (ADT). </li></ul><ul><li>HVCTemplate.blk is located in the EclipsysSunriseClinical Manager clientversionEntdata directory. </li></ul>
    33. 33. Interface Express Load File Template Message Type Event Type Application Name
    34. 34. Interfaces Log showing HVC Template Error HVC Template Error
    35. 35. HL7 Interfaces testing <ul><li>HL7 interface testing is part of the overall HL7 interfaces planning process which includes HL7 interface analysis, HL7 interfaces requirements, HL7 interfaces specifications and HL7 Interfaces Testing . </li></ul>
    36. 36. Eclipsys-Test Utilities Interfaceslite and HL7Test <ul><li>Interfaceslite: </li></ul><ul><li>The Interfaceslite program allows the user to load a data file created by an ancillary department and edit and transmit one or more messages from the file into Sunrise. Interfaceslite is installed as part of the application installation. </li></ul><ul><li>Utility to test the integrity of the HL7 messages and the configuration of SXA Clinical Manager. </li></ul><ul><li>Mimics the HL7 Worker. </li></ul><ul><li>Delivers HL7 into the database bypassing the Interfaces sub system. </li></ul><ul><li>It does not accept HL7 messages from SunriseXA Clinical Manager (not for outbound testing). </li></ul><ul><li>Will show the ACK message from SXA Clinical Manager. </li></ul><ul><li>Do not use the first two header lines in the HL7 push file .Used as placeholder. </li></ul><ul><li>To use, log as a SXA Clinical Manager user with rights to write to the database. </li></ul><ul><li>Must have local admin rights on machine. </li></ul>
    37. 37. Interfaceslite Executable Path
    38. 38. Invoking Interfaceslite <ul><ul><li>To open, double click interfaceslite.exe in the client install folder ( C:Program FilesEclipsys SunriseClinical Manager Clientuild version). </li></ul></ul><ul><ul><li>Login to Interfaces Lite with the appropriate user and password. </li></ul></ul><ul><ul><li>Click the ‘Open’ button and browse for an HL7 message. </li></ul></ul><ul><ul><li>Send the message by clicking the send button. </li></ul></ul>
    39. 39. Using Interfaceslite to test Inbound data to SXA MESSAGE ACKNOWLEGMENT FROM SXA THAT IT RECEIVED THE MESSAGE HL7 message field counter Helper. Shows You the HL7 field your cursor is at Application Accept
    40. 40. FAQ-Interfaceslite <ul><li>How do I debug existing HL7 message? </li></ul><ul><li>The best resource for debugging an HL7 message is the Sunrise Clinical Manager HL7 Mapping Interfaces Reference Guide. This guide describes about all the segments and structure of an HL7 message, their possible values and format. When you are trying to send a message and are getting “AE” application error, read the description of the error message and try to map the context of the error message in the reference guide. </li></ul><ul><li>How can I save an existing HL7 message after modification using interfaceslite? </li></ul><ul><li>Just click ‘Save’ in InterfacesLite. If you are modifying the message in Notepad, make sure you save it with .hl7 extension, otherwise InterfacesLite will not identify the message. Also, one HL7 file can have any number of messages as far as they have message header and are separated by a semi-colon (‘;’). </li></ul><ul><li>How do I know that my HL7 message has been sent successfully through interfaceslite? </li></ul><ul><li>“ AA” is the acknowledgement code for a successful HL7 message transmission. When you click the send button in InterfacesLite, the code is displayed in the ‘Received’ frame. This is the acknowledgment, which SCM has sent back to InterfacesLite that it has received the data and accepts it successfully. If SCM has some errors in receiving the message, it sends an acknowledgment with “AE” code and a reason where the error occurred. </li></ul>
    41. 41. HL7 Test Utility <ul><li>Mimics an Integration Engine. </li></ul><ul><li>Tests messages by delivering them through the interfaces sub-system to the primary active database. </li></ul><ul><li>Used to test the communication of the Interfaces Sub-system. </li></ul><ul><li>Used for Inbound and Outbound Testing. </li></ul><ul><li>It uses the first two header lines in the HL7 push file .Interfaces Lite does not. </li></ul><ul><li>Errors and warnings generated when a message is processed through HL7Test are logged in the normal interface logs. </li></ul><ul><li>Drag the prepared HL7 file on top of the hl7 test.exe and the utility opens up </li></ul>
    42. 42. HL7Test Utility Executable Path <ul><li>HL7Test Utility is installed as part of the Clinical Manager Interfaces installation </li></ul>
    43. 43. HL7Test File Format <ul><li>;client, 192.87.14.210, Port Number (Outbound) </li></ul><ul><li>;client, The Server Name, Port Number (Inbound) </li></ul><ul><li>;HL7ADT </li></ul><ul><li>;PCS </li></ul><ul><li>//first msg </li></ul><ul><li>MSH|||||| </li></ul><ul><li>EVN||||| </li></ul><ul><li>PID||||| </li></ul><ul><li>PV1||||| </li></ul><ul><li>//second msg </li></ul><ul><li>xxxxx </li></ul>Receiving from SXA (Outbound) TCP/IP info Sending to SXA (Inbound) TCP/IP info
    44. 44. HL7 Test GUI Outbound Message
    45. 45. Time to grab a bite ..!!!

    ×