Provide a mechanism to allow (for example) a FHIR V3 resource to be converted to FHIR V4
Hi Tim - would be interested in what sort of use case this would typically support? What would be the end goal? Also, was there a particular API you were thinking in the context, or perhaps you are thinking in terms of more general capability?
Alex - the originating Programme is Interoperable Medicines. The basis is that there are (and almost certainly always will be) multiple versions of FHIR in play. GP Connect for example produces Medications information in STU3, and the new EPS and Interoperable Medicines APIs are being defined as R4. The goal is to make STU3 and R4 FHIR resources interoperable. The concept is to provide organisations with a bridge between versions.
This is of interest to GPIT New Market Enablement, where we are going to have multiple versions of FHIR for any new GPIT foundation system suppliers looking to integrate using APIs and National adapter assets.
We are working on this with medication requests being our first use case.
This feedback board is powered by Feature Upvote.
When submitting your email with a suggestion or comment, Feature Upvote uses your email to
Your email is never displayed to other users. NHS Digital API Management staff will be able to see your email address.
Feature Upvote's Acceptable Use Policy can be summarized as:
Read the full Acceptable Use Policy (in English)
We’ll email you when the status of the suggestion changes. You can unsubscribe at any time with a single click.