HL7 EHR to PowerSoftMD Visit Import Specifications



Similar documents
HL7 Interface Specification Merge LabAccess v. 3.6

IHE Radiology Technical Framework Volume 3 (IHE RAD TF-3)

HL7 Fundamentals. Presented by: Dana McDonough, Carolina Velasquez, & Bing Chen. August 2014

HL7 Interface Specifications

RelayClinical Service Feature Guide RelayClinical Notify

ImagePilot. HL7 Conformance Statement. Manufacturer: 1 Sakura-machi, Hino-shi Tokyo , Japan

HL7 Conformance Statement RadCentre. Release

ELR Clarification Document for EHR Technology Certification

Generic EHR HL7 Interface Specification Abraxas v. 4

HL7 Format and Electronic Sharing

DIAGNOSTIC TEXT AND OTHER TRANSCRIBED REPORTS MESSAGE SPECIFICATION

HL7 Interface Specification. HL7 Interface 1.2

HL7 Conformance Statement

UHIN STANDARDS COMMITTEE Version 2.0 Radiology Report Standard

HL7 Conformance Statement

HL7 Interconnection Guide v1.1

JiveX Enterprise PACS Solutions. JiveX HL7 Gateway Conformance Statement - HL7. Version: As of

Introduction to Epic Bridges. Empowering Extraordinary Patient Care

PMS / EMR Message Specification (Version 2.3.1) (ADT, AL1, OBX, SIU, DFT, PPR (PRB), ORM, VXU)

Message Specifications Guide

EHR-Laboratory Interoperability and Connectivity Specification (ELINCS) Version 0.2 DRAFT

Syndromic Surveillance Event Detection of Nebraska (SSEDON) Flat File Implementation Guide for Inpatient Syndromic Surveillance

HL7 Interface Specification Merge Eye Station v. 11.3

Clinical Document Exchange Integration Guide - Outbound

278 HEALTH CARE SERVICES REVIEW REQUEST AND RESPONSE COMPANION GUIDE

ShadowLink 2. Overview. May 4, ONLINE SUPPORT emdat.com/ticket/ PHONE SUPPORT (608) ext. 1

How To Get A Medical Record On A Medical Device

HL7 Customization Guide

Philips Innovation Campus Bangalore India. Issued by:

Installation and Maintenance of Health IT Systems: System Interfaces and Integration

HEALTH INFORMATION STANDARDS COMMITTEE FOR ALBERTA

Additional Information Message Implementation Guide

ELR Clarification Document for EHR Technology Certification V1.1

Medical device security

Interfacing Boot Camp

Notes Interface Specification HL7 format

Syndromic Surveillance Event Detection of Nebraska (SSEDON) HL7 Implementation Guide Inpatient Syndromic Surveillance

D* SEE SAP DIR DIGITAL SIGNATURE LOG FOR APPROVER NAME AND DATE OF APPROVAL

DBaaS Using HL7 Based on XMDR-DAI for Medical Information Sharing in Cloud

HEALTH CARE CLAIM: INSTITUTIONAL 837 (004010X096A1)

DEPARTMENT OF HEALTH & MENTAL HYGIENE MEDICAL CARE PROGRAM

20/20 Integration Guide

Illinois Veteran Grant (IVG) Online Payment Manual Chapter 4

National Patient Information Reporting System: National Data Warehouse

810 Invoice ANSI ASC X12 Version 4010

Michigan Care Improvement Registry HL Specification for Vaccination Messages. Document Description

How To Write A Health Care Exchange Transaction

Meaningful Use Business Process Mapping Questionnaire. Meaningful Use Business Process Mapping Questionnaire. Contact Information

ANSI X12 version Text Message

IHS Pharmacy-Automated Dispensing Interface System (BOP)

Overview. LATITUDE Patient Management. EMR Integration Testing Scenarios

ANSI X12 version Advance Ship Notice

850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft

PERSHING STANDARD FILE LAYOUTS

Michigan Pulse Oximetry Screening for Critical Congenital Heart Disease

Electronic Syndromic Submission for Emergent and Ambulatory Data to the Michigan Department of Community Health

MICHIGAN SECRETARY OF STATE ELECTRONIC INSURANCE VERIFICATION (EIV) TRANSMISSION OPTIONS AND FILE FORMAT GUIDELINES

Deployment Planner. inexx Novo Grid Practice Agent HW Requirements.pdf

Clearinghouse Screen Instructions for ANSI837

MHS EMR Program. EMR HIE Integration Toolkit

Using EHRs to extract information, query clinicians, and insert reports

214 Transportation Carrier Shipment Status Message

Sanford Health Plan. Electronic Remittance Advice 835 Transaction Companion Guide Trading Partner Information

Issue 1.1, February agreed-upon by EDI Working Group of ECR Poland

IHE IT Infrastructure Technical Framework. Volume 2b (ITI TF-2b) Transactions Part B Sections

Design of Internet Protocols:

Text Integration Utilities (TIU) Generic HL7 Interface Handbook

Welcome to the Data Analytics Toolkit PowerPoint presentation on EHR architecture and meaningful use.

ANNEXURE - I. Back-office Interfaces

The EDI 810 specification is separated into logically distinct groups, which are composed of particular segment types.

Motor Insurance Database Phase II 4 th EU Motor Insurance Directive

HIPAA EDI Companion Guide For 270/271 Eligibility Inquiry & Response Companion Guide Version: 3.0

Sunrise Acute Care (SAC) Module 1 New Provider Basic Course

Project Initiation Report HealthInsight HIE

Accounts Payable Expense Distribution Tables

EHR Meaningful Use Guide

834 Benefit Enrollment and Maintenance

Purpose of the 270/271 Health Care Eligibility Benefit Inquiry and Response

A method for handling multi-institutional HL7 data on Hadoop in the cloud

MicroMD EMR version 7.6

ZAN HL7 Interface. Installation and Specifications Manual Part Number : *************ENG Version / Revision : A

Meaningful Use Stage 2 Certification: A Guide for EHR Product Managers

HL7 Onboarding Guide for. May 2015 v3

Electronic Data Interchange

LIS Interfaces: Basics, Implementation and Pitfalls

Care360 EHR Frequently Asked Questions

Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010

Connecticut Department of Public Health Electronic Laboratory Reporting HL7 v2.5.1 Message Validation Tool User Guide

Masimo Patient Safetynet HL7 Interface Specifications

Job Cost Report JOB COST REPORT

Stage 2 Eligible Professional Meaningful Use Core Measures Measure 15 of 17 Last Updated: August, 2015

Transcription:

HL7 EHR to PowerSoftMD Visit Import Specifications Data Tec, Inc. www.powersoftmd.com 1 P a g e R e v M a y 2 0 1 3

Introduction HL7 EMR to PS Interface Specs PowerSoftMD uses HL7 2.3.1 specifications. The following pages outline our specifications for building a file to send to PowerSoftMD of Financial Information. PowerSoftMD itself does not transmit or receive Messages. The EMR is responsible for setting up a secure folder on the Clients (Doctors Office) computer to send and receive files from. This folder must be on the same Windows shared drive as the PowerSoftMD folders are located. We recommend a structured folder name, for example: H:\HL7\XYZCorp The sending company can use a VPN or service like HyperSend if they need to transmit files. Whatever is agreeable with the Client (Doctors Office) and is encrypted and secure to HIPPA standards. Again, the secure transmission is between the sending Company and the Client (Doctors Office), Data Tec is not involved or responsible for this link or transmission service in any way. Technical Basics Message delivery: Data Tec is not responsible for data delivery or pickup. We look for and leave messages in specified local computer directories. Standard HL7 message structure, Segment delimiters <CR> Messages delimiters <LF> - field delimiter ^ - component delimiter ~ - repeat delimiter \ - escape character & - sub-component delimiter The following escape fields are defined. \F\ field separator character \S\ component separator character \T\ subcomponent separator character \R\ repetition separator character \E\ escape character No Acknowledgement messages are utilized. 2 P a g e R e v M a y 2 0 1 3

HL7 Message Type Financial Transaction Segments Required Description MSH Y Message Header EVN O Event Type PID Y Patient Demographics PV1 Y Patient Visit Information FT1 Y Financial Transaction DG1 Y Diagnosis Sample MSH ^~\& SendingApp FamilyMed PowerSoftMD FamilyMed 201212190725 DFT^P03 201212190725 P 2.3.1 EVN P03 201212190725 PID 1 00208 A8401 SMITH^JOHN^J 19700101 M W^White 140 3rd St^^Sparks^NV^89431 3148953333^^^Test@aol.com 8772581281 English S 608889210 Hispanic PV1 1 9876543210^WOLFMEYER^SANDY FT1 1 1234567890 20061114 CG 1 052.9^Chickenpox~949.0^Burn 9876543210^WOLFMEYER^SANDY 99212^RETURN VISIT-FOCUSED 25 DG1 1 052.9^Chickenpox^ICD9CM DG1 2 949.0^Burn^ICD9CM * All messages are pipe ( ) delimited and terminated by a carriage return/linefeed * Some fields (denoted on the segment definitions) are caret ( ^ ) sub-delimited *Values for the "required" field: Y = Yes; we will always populate this field O = Optional, can be sent, not required All other fields should always be blank or its values will be ignored * Date/Time Values are always formatted: Date = CCYYMMDD Time = HHMMSS Date/Time = CCYYMMDDHHMMSS 3 P a g e R e v M a y 2 0 1 3

MSH - Message Header Definition 0 Message Qualifier Y MSH 1 Separation Character Y 2 Encoding Characters Y ^~\& 3 Sending Application Y SendingApp 4 Sending Facility O FamilyMed 5 Receiving Application Y PowerSoftMD 6 Receiving Facility O FamilyMed 7 Date/Time Y 201212190725 9 Message Type Y DFT^P03 9.1 Message Type Qualifier Y DFT 9.2 Message Trigger Y P03 11 Production Flag O P 12 Version Y 2.3.1 4 P a g e R e v M a y 2 0 1 3

EVN - Event Type Definition 0 Message Qualifier Y EVN 1 Event Type Code Y P03 2 Recorded Date/Time Y 201212190725 5 P a g e R e v M a y 2 0 1 3

PID - Patient Demographics Definition 0 Message Qualifier Y PID 1 Sequence Number Y 1 2 Patient Account Number Y 00208 5 Patient Name Y SMITH^JOHN^J 5.1 Patient Last Name Y SMITH 5.2 Patient First Name Y JOHN 5.3 Patient Middle Initial Y J 7 Date of Birth Y 19700101 8 Gender Y M 19 Patient Social Security Number O 608889210 6 P a g e R e v M a y 2 0 1 3

PV1 - Patient Visit Information Definition 0 Message Qualifier Y PV1 1 Set ID Y 1 7 Attending Provider Y 9876543210^WOLFMEYER^SANDY 7.1 Provider ID Number (Secur) Y 9876543210 7.2 Provider Last Name Y WOLFMEYER 7.3 Provider First Name Y SANDY 7 P a g e R e v M a y 2 0 1 3

FT1 - Patient Visit Information Definition 0 Message Qualifier Y FT1 1 Set ID Y 1 2 Transaction ID Y 1234567890 4 Transaction Date Y 20061114 6 Transaction Type Y CG 19 Diagnosis Codes O 052.9^Chickenpox~949.0^Burn 19.1 Diagnosis Code Y 052.9 19.2 Diagnosis Description Y Chickenpox 20 Performing Provider Y 9876543210^WOLFMEYER^SANDY 20.1 Provider ID Number Y 9876543210 20.2 Provider Last Name Y WOLFMEYER 20.3 Provider First Name Y SANDY 25 Procedure Code Y 99212^RETURN VISIT-FOCUSED 25.1 Code Y 99212 25.2 Procedure Name Y RETURN VISIT-FOCUSED 26 Modifiers O 25 8 P a g e R e v M a y 2 0 1 3

DG1 - Patient Visit Information Definition 0 Message Qualifier Y DG1 1 Set ID Y 1 3 Diagnoses Code Y 052.9^Chickenpox^ICD9CM 3.1 Code Y 052.9 3.2 Diagnosis Description Y Chickenpox 3.3 Coding System Y ICD9CM 9 P a g e R e v M a y 2 0 1 3