Dealer Login

No healthcare information system is an island

Data must be shared across PM, EHR and other systems for efficient service to patients and in order to comply with regulations. We are the experts on building interfaces that inter-connect disparate healthcare IT systems.  See a full listing here.

The United States spends more on healthcare per capita and as percentage of its GDP than any other nation. But today’s healthcare IT is still a hodge-podge of clinical, financial, imaging and other systems that were developed over decades. Each system is an island with a rapidly growing need for sharing data and de-duplication. These requirements can be extremely expensive and time-consuming to meet.

Micro-Office’s Interconnection Solutions

We are the experts on building interfaces that interconnect disparate healthcare IT systems. Our interfaces transfer data between hundreds of systems, delivering thousands upon thousands of data transactions and files each and every day on behalf of physician practices and clinics.

The Interfaces

Our interfaces are powered by a powerful, high performance engine, AnyExchange™, that supports HL7 and CCDA, and connects directly to PMS, EMR and other systems. It works effectively for small practices and scales to very high volumes of transactions quickly and reliably. The hub-and-spoke architecture enable us to add a new interface that takes immediate advantage of all the built-in capabilities.

  • Highly secure
  • Import / Export information in and out of any system
  • Data types include demographics, appointments, financials, transactions, master files, lab orders and results, prescriptions, documents, images and other clinical information
  • Support HL7 and custom formats
  • Communicate via files, TCP sockets, APIs and Web services
  • Support mapping values between systems such as account numbers and provider codes
  • Match patients using flexible rules on name, date of birth and social security number
  • Provide modes of operation including snapshots of data and changes as they occur
  • Invoked interactively or in the background
  • Scheduled, one time, or continuous operation
  • Scaling to high data volumes with minimal system resources

Our proven library of interfaces is available for connecting healthcare systems according to practice and clinic requirements. With our expertise and AnyExchange™ engine, we can quickly deliver customized interfaces for any system.

Types of interfaces we handle

With an EHR, the typical interface will send Demographics and Appointments from the PM to the EHR. The EHR may also send Charges back to the PM system. This assumes that the PM is the “master” for demographics. In some situations, the EHR is the master, and it sends demographics, appointments and charges to the PM. The challenge with the latter is that often the EHR insurance and responsible party info is not as robust as needed by the PM.

When a practice sees patients in conjunction with a hospital, the hospital IT system can be the source for demographics to the PM system, as well as charges. The challenge with a hospital system is that typically every patient is assigned a new account for each stay; whereas in a PM, the same account is used. Also, many hospital systems to not use consistent coding of insurance plan information.

For labs, there are two levels of interfacing. A simple level is to send demographics to the lab. This may be done via a continuous feed, of all demographics from the PM. Or it may be done on a request basis; the Lab IT system sends a request for a specific patient.

The second level is more robust: Orders are sent from the practice to the lab system, and Results are returned from the lab to the practice.

Many practices still use transcription systems and services. The transcription process can be streamlined using templates when there is a demographic interface to the transcription system.

Practices will often have Radiology equipment, including X-Rays, Mammograms and Ultrasound. This equipment needs a worklist of patients, and this can be communicated via an interface. If an ordering system exists within the practice system, the interface will be straightforward. Often, however, the worklist is inferred from the practice scheduling system. This involves mapping the appointment data to the corresponding order data needed by the modality.

Micro-Office has developed interfaces between more than 130 systems.  You can see a full list of interfaces that we've written right here (bear in mind when you visit the link, even if you are using a system that doesn't appear in the list there, we can probably write the interface to or from it.)