Healthcare IT that moves patient data safely and on time

Where our work involves access to protected health information, we can enter into a BAA as part of the contract. We also design cloud environments so that your cloud provider’s BAA covers the services in use.

Yes. We start with an inventory and documentation pass, add monitoring and alerting, then support the channels under an agreed SLA. This covers both commercial Mirth Connect (NextGen, version 4.6 onwards) and the open-source Open Integration Engine fork.

Usually by adding a FHIR server or facade that maps your HL7 v2 and CCDA data into FHIR R4 resources conforming to US Core, secured with SMART on FHIR. Your source systems do not need to change on day one.

We integrate with major EHRs through their supported interfaces: HL7 v2 feeds, FHIR APIs and vendor app programmes. Some vendor programmes require your organisation to sponsor or register the integration, and we work through that with you. We are not a certified partner of any EHR vendor.

A standard HL7 v2 feed between two systems that are already reachable often takes days to a couple of weeks, including testing. Analyser interfaces, FHIR facades and HIE onboarding take longer, mostly because of partner testing windows. We give you an estimate after the discovery call.

Clinic Answering Service is built for US practices and HIPAA requirements. Our India-focused products (dental, physio, pathology and veterinary) are built for Indian clinics and data-protection law. Ask us for the security documentation of any product you are evaluating.