When we looked at the market, we discovered that most folks did not know. Even within our own community, folks didn’t really know how to answer the question.
The first outcome of this project is that we can provide the answer with an emphatic “Yes!” Rhapsody is an effective and efficient platform for developing interfaces using the FHIR® standard. It has these capabilities right now — and considerable flexibility in how you can best develop and implement them.
The project took a ‘design thinking’ approach. We started by looking to discover who our users were and what they needed to know. These users included not only our customer-facing representatives, but also customers, including CTOs, developers and analysts, integration managers, and support staff. What do they need to know? What do they need to do?
From there we looked at what we could create to help meet those needs. We addressed several use cases. We evaluated how our different tools fared and developed better practices along the way. We prototyped, evaluated, and documented.
Our goals were lofty, and, in the end, we produced material geared at both our internal staff as well our customers and the broader interoperability marketplace.
One of our secondary goals was to identify strengths and gaps in our offering and create a FHIR-focused roadmap for the platform. This required learning more about how FHIR is done out in the wild. And that is an adventure all its own.
By the end of the project, we determined that Rhapsody makes for quite a robust FHIR development environment, and we are continuing to work on turning this into assets that we can make available to our customers.
We have produced several documents to help you get started with FHIR in Rhapsody. Download:
FHIR® is the registered trademark of HL7 and is used with the permission of HL7. The Flame Design mark is the registered trademark of HL7 and is used with the permission of HL7.