Hi, enum values (aka ValueSet) in FHIR seem to be converted to strings in MedPlum's GraphQL server. For example, ExplanationOfBenefits.outcome are turned into strings (see link and screenshot). Why is that? https://build.fhir.org/explanationofbenefit-definitions.html#ExplanationOfBenefit.outcome

Hi @jnak Medplum uses FHIR R4. In R4,

ExplanationOfBenefits.outcome

is a "code" type, which is represented as a simple string: https://hl7.org/fhir/r4/explanationofbenefit.html

Ah got it! 🤦‍♂️ I didn't realize a major FHIR migration was already on the horizon :/ Hopefully, Medplum will provide some tools and strategies to help with it. Thank you!

@jnak - here's our post on R5 - https://www.medplum.com/blog/fhir-r5 - the anchor tenants for the FHIR Ecosystem (Big EHR like Epic & Cerner, CMS/ONC and Apple) have made large investments in R4 and haven't made specific anouncements. We are tracking it!

How are you thinking about the migration? Will MedPlum be able to ingest FHIR 4 resources and serve them as FHIR 5?

That's the plan eventually, but the first step is to enable R4B which is supporting the backward compatible parts of R5 in R4.

@jnak - there are some more details in this GitHub Discussion: https://github.com/medplum/medplum/discussions/2813 > How are you thinking about the migration? Will MedPlum be able to ingest FHIR 4 resources and serve them as FHIR 5? That is a stretch goal. The first order of business is robust pure R4 and robust pure R5 separately. Once that is ready, then automatic conversion between R4-R5 follows. You can read more about automated R4-R5 conversions using FHIR Mapping Language here: https://build.fhir.org/ig/HL7/fhir-extensions/conversion-registry.html As you can see, it's not a perfect translation yet.