Release Notes History

This is support for the R4 (v.4.0.0) official FHIR release. In this release, XES Module for FHIR including the FHIR server, web portal, and processing routes has been migrated to R4.

When do I need it?

When you have to store and convert your data to/from the R4-compliant FHIR server, and when you expect your SMART on FHIR applications to be R4-compliant.

What are the benefits?

You can leverage the out-of-the-box benefits of the first normative FHIR release that includes additional stability for the standard's elements. As these elements have now been tested and are mature enough to remain stable, this means that it is much easier to use them and you save the costs on development and maintenance. The R4 release ensures a longer-lasting and more stable platform along with greater interoperability.

Da Vinci use cases help Payers and Providers improve clinical, quality, cost and care management outcomes. XES Module for FHIR is distributed with a set of preconfigured XEServer profiles that illustrate the following Da Vinci use cases:

• Scheduling an appointment:
• Da Vinci 1 Scheduling Generic Profile (for R4-complient EMR)
• Da Vinci 1 Scheduling Cerner Profile (adopted for Cerner EMR)
• Payer-Provider Data Exchange (PDex):
• Da Vinci 2 Payer Provider Ex Generic Profile (for R4-complient EMR)
• Da Vinci 2 Payer Provider Ex Cerner Profile (adopted for Cerner EMR)
• Coverage Requirements Discovery (CRD): Da Vinci 3-4 Coverage Requirement Discovery and Medication Reconciliation Profile
• Medication Reconciliation Process (MRP): Da Vinci 3-4 Coverage Requirement Discovery and Medication Reconciliation Profile.

When do I need it?

When you want to promote interoperability, enable Providers and Payers to electronically exchange patients’ data with each other and provide them with quick access to the required data. For example, when you enable the scheduling of an appointment in an external EMR system.

What are the benefits?

By accessing the patients' data shared between Providers and Payers, Providers get all the available details on observations, diagnoses, allergies, and so on without having to repeat the same tests and procedures again and that drastically reduces costs.

FHIR components allow you to perform the following actions with the FHIR servers:

• Perform CRUD operations on a FHIR resource using the FHIR Resource component
• Search for FHIR resources using the FHIR Search component
• Perform flexible custom actions by building your own request to the FHIR server.

When do I need it?

When you have to submit, retrieve, delete data to/from FHIR servers, perform search or other server request through secure connections using Basic, Digest, or OAuth 2.0 authorization types.

What are the benefits?

With these components, you can easily set up FHIR-related interactions in your XEServer routes without having to use complex logic and several operations. This drastically simplifies communication with the FHIR server and you save the time that you would otherwise have to spend on route implementation and maintenance.

The CCD to ECDA component allows you to convert CCD to the ECDA (Edifecs CDA) format that has been adopted to simplify further translation to any other format including FHIR.

When do I need it?

When you have to convert CCD data to the human-readable and user-friendly ECDA format that can be easily translated to other formats including FHIR.

What are the benefits?

This saves costs and the time you spend on data conversion implementation. Since the most difficult task of translating a complex structure of CCD data is resolved with this component, this allows you to proceed with further down-the-stream translation to the required format.

The CMS mandate that requires patients to be able to access their data through the Blue Button 2.0 interface has been implemented. The Blue Button assumes the use of FHIR technology for data formatting and retrieval.

When do I need it?

When you have to provide patients, primary care physicians, or research organizations with access to patient data. You can use it when:

• you have to convert 837 claims and 835 claim responses EDI files into FHIR Explanation Of Benefit (EOB) resources
• view FHIR EOB resources on the web portal
• download EOB resources in the FHIR format
• download EOB resources in the HTML format.

What are the benefits?

You get an out-of-the-box implementation of the CMS mandate. You can access EOB resources in the FHIR format or in the user-friendly HTML format.

A care coordination with the providers that do not support the FHIR format.

When do I need it?

When you need to facilitate the care coordination with the providers that do not support the FHIR format. To do this, you can:

• convert CCD to FHIR and in the reverse,
• convert HL7 data to FHIR to be able to exchange patients' medical history.
• extract a required patient’s FHIR data from the EMR system and add the data to your FHIR server.
• share the patient's Clinical Chart with other health plan's (export FHIR data to CCD).

What are the benefits?

You save time and money having rapid adoption of FHIR standards for organizations with basic or no prior experience, as the solution comes as an easily installable package, also leveraging flexibility and ease of the FHIR standard. You gain reference orchestrations for business scenarios, such as quality measures, care coordination, attachments and others.

XES Module for FHIR converts eligibility requests submitted in the FHIR format to HIPAA transactions to make them acceptable by your EDI-compliant back-end system.

When do I need it?

When you want to provide patients with a convenient way to confirm eligibility coverage using a web portal. XES Module for FHIR also allows you to create FHIR resources based on EDI eligibility responses.

What are the benefits?

You are provided with a FHIR standards database that contains out-of-the-box guidelines for the recent HL7 FHIR standards that allow for building maps, validation and integration routines. You have a competitive advantage by extending the capacity of existing FHIR servers or patient repositories to any partner, by using pre-built maps between industry standards (HIPAA, HL7, CCD) and FHIR resources.

XES Module for FHIR collects patient-related resources (demographics, encounters, procedures, and so on.) in real time and performs accurate up-to-date quality measures against a required provider.

When do I need it?

When you need to evaluate the quality of providers' work, calculate patient outcomes without having to buy or build expensive Quality Measure Engines. This helps you distribute the payment properly among providers.

What are the benefits?

You can have integration between FHIR and existing back-end systems (Adjudication, Membership, etc.), integration with current back-end systems with pre-configured maps and routes in a productized fashion. You can jump-start the development of FHIR-based projects or use cases with proven technology thus saving your time and money.