As of January 1st, 2021, Medicare Advantage, Medicaid, CHIP, and plans on the federal Exchange beginning in 2012 are required to support a standardized FHIR API. Fast Healthcare Interoperability Resources (FHIR) is a standard for exchanging electronic health records that is easier to implement as it uses current API technology. This standard facilitates interoperation for legacy systems, allowing for a much easier integration. It also emphasizes the goal that the exchange of healthcare information to health care providers and individuals should be easily and securely accessible across a variety of devices and third party medical applications.
With regulations such as the CMS Final Rule, patient data such as the below needs to be available and shareable:
- Patient Record API
- Provider Directory API
- Payor to Payor Transfer
- Notification of discharge and other events
Adding a FHIR API on top of your Electronic Health Record (EHR) system connects disparate data across systems to standardize patient data and create accessibility to payers, providers, and patients. Patients with providers in different healthcare systems can access a single portal. This portal integrates data from different formats and delivers a comprehensive view of the patient (including allergies, care plans, health issues, and medications).
Implementing MuleSoft with Perficient
Plan. Expand. Optimize. A Cloud Migration Workbook.
Strategize the next steps of your organization's application modernization journey leveraging our experts' pragmatic approach.
Beginning with an enterprise tool allows you to address challenges once, rather than relying on a rapid fix to meet requirements. This helps relieve additional costs down the road, as non-interoperability integrations are typically not handled by niche vendors. Perficient partners with MuleSoft to improve clinical, financial, and operational efficiency. We leverage the MuleSoft Accelerator for Healthcare, which includes pre-built APIs, integration templates, connectors, and reference architectures constructed to take on real-time loads without sacrificing data governance or quality.
Coupled with the MuleSoft Accelerator, we review the current environment, data resources, and healthcare resources to build architecture and proof of concept with patient and provider data while navigating the complexities of regulatory reform. We’ve built a jumpstart to help you get your platform up and running with at least one integration within four weeks – with built-in support following the integration:
- Week 1: Finalize architectural elements, such as the approach for FHIR and other standards
- Week 2: Instantiate services to ensure security and availability both internally and externally
- Week 3: Set up initial integrations to key services using the FHIR standard
- Week 4: Test and launch solutions in a production environment
Perficient’s Healthcare Industry Experience
In addition to real time healthcare integration, Perficient has worked with industry standards such as HL7 and CCD/CCDA to transfer patient records to a variety of systems and data repositories. We understand healthcare data as well as how to safely transport, store and use it. We have assisted leading healthcare providers with their transformational journeys to better align with ever-changing business needs while modernizing their IT environment.
Recently, our ability to build API-led connectivity architecture in MuleSoft with interoperability design patterns and best practices provided an efficient digital health solution with a single membership and billing system. We were able to streamline member enrollment and termination processes, member payment transactions, and real-time payment processing. By incorporating matter management, document management, and legal hold, we increased efficiency, transparency, and collaboration. Our solutions were delivered with the client’s best interests in mind and followed by continued business-critical support.
Raj Palla, MuleSoft Practice Director, and Mike Porter, Managing Principal – Healthcare Practice, also contributed to this post.