Medical Business Systems has developed the Connectivity Clearinghouse that enables multiple medical software programs to exchange information. Eliminate duplicate entry of data and streamline your workflow, we can show you how.

1. Is your EMR holding your
data hostage?

2. Medical Business
Systems
Presents
Connectivity
Clearinghouse

3.  At Medical Business Systems, we have domain
expertise in medical systems software.
 Historically, MBS has its origins in the practice of
radiation oncology.
 Iridium Suite, our cloud-based practice
management system, was our initial product
offering and it remains an innovative medical
billing solution.

4. Why was the CC developed?
 The Connectivity Clearinghouse grew out of
a need to connect Iridium Suite with a wide
array of third party systems.
 It is proprietary custom software that
facilitates efficient, flexible and cost
effective interoperability between
disparate medical data systems.

5. How does the CC work?
The CC does not require data file format
compatibility between systems.
It receives output from the system
transmitting the data and translates that
output into a format that can be processed by
the receiving system.

6. What type of data is compatible with
the CC?
 The CC works with multiple data file formats
including DICOM, HL7, XML, and ANSI EDI x12.
 In addition, the CC can easily customize HL7 data
fields allowing systems to exchange a wider variety
of information.
 The Connectivity Clearinghouse also supports a
wide range of secure communication protocols for
increased versatility.

7. What are the steps to implement the
CC?

MBS establishes communication with the third party medical
data systems who wish to achieve interoperability.

MBS works with all parties involved to gain a complete
understanding of each organization’s goals as they relate to
the exchange of data between the systems in question.

The third party systems provide their data file specifications
and communication protocols to Medical Business Systems
for analysis.

8. 
MBS analyzes the file specifications, working with the third
party organizations to clarify any ambiguities and to solidify
MBS’ understanding of the data systems and their
interoperability needs.

The integration fee is determined based upon the scope of
the project and customization requirements.
›
The implementation timeline is determined based upon the
availability and accessibility of the third parties in
combination with the scope of the project.

9.  MBS creates a Custom Integration Agreement which outlines
the specifications, expectations, limitations and costs
associated with the project.
 Upon execution of the Agreement by all parties, MBS
commences work on the project at the agreed upon time as
established in the Agreement.
 When MBS has completed its integration work, the
organizations will develop a test schedule and will provide
test files to validate system interoperability and identify any
issues which require correction.

10.  After the beta testing has been successfully completed, the
integration will go live.
 While every effort is made during beta testing to ensure full
compatibility, on occasion due to test data deficiencies, issues may
present themselves only after going live with real world data.
 After go live, the Connectivity Clearinghouse will expect to receive
data according to the prescribed file formats. If the data is not
received in the exact manner expected, then the message in
question will ‘fail validation’.
 Messages which fail validation are rejected and do not pass
between the systems.

11.  MBS is alerted when messages fail validation and will attempt
to correct the error and re-transmit the message when
possible.
 If the data which is missing or erroneous is beyond the scope
of MBS’ ability to repair unassisted, then MBS will contact the
appropriate third party staff members to seek their assistance
in resolving the matter.
For further information:
Contact Susan Morrison
by telephone: (775)453-3193 or
by email: susan@iridiumsuite.com