FREQUENTLY ASKED QUESTIONS
What systems does the Interoptex iPaaS integrate with?
The Interoptex iPaaS integrates with all major EMR and Practice Management systems, including but not limited to Meditech, Epic, Cerner, Athena, CPSI, eClinicalWorks, Allscripts, and many more. We can integrate with any system that can send or receive data, regardless of format. The only requirement is that our iPaaS must have an endpoint for inbound and outbound data, be that a TCP/IP connection, a RESTful API, an SFTP client or server connection, or even a direct database connection.
What data formats can Interoptex iPaaS process?
The Interoptex iPaaS can process all major healthcare data formats, and even custom formats! We process everything from HL7 v2 (ADT, ORU, MDM, ORM, DFT, MFN, etc.), to C-CDA documents, to X12 formats (835, 837, 270, 271), to custom-made formats with set delimiters or set field widths. Chances are if we can get the data, we can process it.
What exactly do you do with my data when you pick it up from one endpoint and deliver it to another?
We include any necessary code for data-shaping and business logic to deliver the dataset to the receiving endpoint. This work, which most integration partners charge exorbitant fees to render, is built-in to your subscription fee. Our integration guides will work directly with your team during implementation to re-shape data and make appropriate decisions about how the data should be delivered to the receiving endpoint. This could take the form of stripping special characters for certain data points, matching against specific facility ID’s to route your data to a specific destination based on a data point within the dataset, or cross-walking a numeric identifier to an NPI, for instance.
Are you willing to cross walk data points in our data set?
Yes! We excel at data mapping and are happy to maintain crosswalk tables specific to your organization. We will work with your team to establish a protocol for updating any crosswalk tables we host for data mapping.
We want to make a RESTful API call to give you our dataset. How do we do that?
Interoptex has a secure API call that we give to clients that prefer to post their dataset to us. This API call uses basic auth, JSON or XML formatting, and only includes three data points, the first is a proprietary client identifier, the next is a text string indicating the format of your dataset (e.g. ‘XML’, ‘C-CDA’, ‘837 Batch’), and the final datapoint is the actual dataset generated by your system. We’ll take it from there.
I've heard that you have a subscription-based plan. Why is that, and what do I get for my fee?
Yes, Interoptex uses a subscription-based billing plan to lower the barrier to entry for growing healthcare organizations that need to integrate quickly, but don’t have an enormous capital budget to help them get started. Your Interoptex iPaaS subscription fee includes all upfront development, implementation support (including direct contact with your system vendors), and around the clock monitoring.
Are you HIPAA Compliant?
Yes! We ensure all of the following controls are in place to ensure HIPAA compliance for our customers:
- All data is encrypted at rest and in transit.
- All iPaaS servers are installed with an aggressive IDS, IPS, DLP, antivirus, and antimalware agent that reports detected threats to our IS team in real time.
- Only appropriate personnel on the Interoptex team will have access to your data.
- We maintain monitoring and logging at the network, OS, and interface levels around the clock and respond to any detected high priority incidents on nights or weekends.
- Check out documentation on additional controls.
How do I know how much data my Interoptex iPaaS instance is processing?
We can provide reporting for:
- What formats of data you’re processing
- How much data of each type has been processed
- How many of your transactions have been successful, and if they haven’t been successful, what error codes were generated during processing
Interoptex iPaaS billing is based on the number of integrations. How do you define an integration?
Interoptex defines an integration as a connection to an individual instance of a medical system (or endpoint, network folder, database, or SFTP folder used by an instance of a medical system) for purpose of transmitting data. Each integration includes 3 data models. Examples of data models depend on the formats involved in the integration, but typically a single data model would be considered:
- A single HL7 message type in HL7 integrations
- A single API call (GET Patients, GET Providers, etc.)
- A single proprietary CSV, XML, JSON, or flat file
- A single-system generated CCD
- For clarity we’ll provide a billing example: In this scenario the Client has two customers sending data through IPAAS. One of the Client’s customers, Hospital Network A, has two systems sending data, and both systems are sending inbound CCD’s. This would be counted as one billable integration to hospital A, because only two of the three available data models are being consumed for that integration. Client also has a second customer, Hospital Network B, which has five sites all using a single EMR. This single EMR is sending several types of HL7 data. ADT, SIU, and DFT. The total number of integrations for Hospital Network B would also be one. Even though these the data models/messages are comprised of data from five sites, they are coming from a single source EMR. Between Hospital Network A, Hospital Network B, and the Client’s dedicated connection, the Client would receive a monthly bill from the Provider of two billable integrations.
Have a more questions? We have answers!
If you have additional questions or would like more information, we would love to hear from you.
Just click the link below to access our contact form. Someone will contact you soon!