A key quality of care benefit of an EHR is its ability to create, send out and track the provider's orders and then electronically review and route the results of those orders into the patient's record. Due to many national efforts, HL7 standard language is used to create these interfaces. When the interfaces communicate back and forth with your EMR, results can be provided to the clinician for review prior to posting into the patient record.Some specialties receive as much as 70 percent of health care information from outside sources, including information from hospitals, labs, diagnostic imaging centers, payers, referring physicians, patients and pharmacies.The most common interfaces to manage that flow of patient information include:
» Practice management system
» In-house and outsourced Labs
» Medication management (in house pharmacy or e-prescribing)
» Pathology
» PACS (picture archiving and communication system)
» Inbound faxes (typically comes with the EMR)
Step 1 - Build an Interface ScheduleLab interfaces take the most time to coordinate. Contact your lab representative at least 90 to 120 days before you plan to go live on the system.The vendor's e-prescribing component must be certified (such as by CCHIT or SureScripts/RxHub) for you to participate in CMS' e-prescribing Reimbursement Incentive program. You may want to use the e-prescribing component early in your training.Your EMR vendor will work with you to coordinate the interface with your PM system. Count on 60 days if they have interfaced with your PM system. Add 45 to 90 days if this is their first interface with your PM system.Step 2 - Test the InterfacesFifteen to thirty days before training test the interfaces to see if you can:
» Order a lab test from the EMR to the Lab
» Receive results from the Lab into the EMR
» Produce a billable encounter into your PM system. Lab systems often push multiple bills for the same encounter. Do NOT skip this step.
Step 3 - Approve the InterfacesZero to fifteen days before training approve the interface and move it into production.Step 4 - Move the Interface into ProductionYour vendor will work with you to move your interfaces into production for training and go-live.
After 15 years helping clinicians move into health IT, Carolyn now helps providers and caregivers use technology to coordinate care, reduce errors, and support loved ones with chronic conditions. She has co-authored 20+ books on privacy and security.
When a HIPAA breach hits, delay costs money. Build your response team before you need it: a data privacy attorney first (to help protect the investigation under privilege), then forensic and IT consultants, media relations, and HR.
I am asked that question almost weekly. While the answer has traditionally been “no,” the legal landscape is shifting and the risk of being sued continues to increase.
Let’s
A party’s responsibilities under HIPAA generally come from two sources - the law itself and the business associate agreement entered into between the covered entity (the health care provider or
June 7, 2013. Today, HHS published in the Federal Register "Technical Corrections to the HIPAA Privacy, Security, and Enforcement Rules" that were published on January 25, 2013, as
As a clinician, you want to know if data being entered into the system is accurate, clean, correct and useful. Data validation often called "validation rules" or "
The secure exchange of health information is dependent on both the practice and EHR vendors facilitating the secure electronic transactions and extracting data for reporting quality measures. Even early adopters
Pay-for-Performance: The use of incentives to encourage and reinforce the delivery of evidence-based practices in the health care system transformation that promote better outcomes as efficiently as
Interoperability: The ability to exchange and use information (usually in a large heterogeneous network made up of several local area networks). Interoperable systems reflect the ability of software and hardware