Ontoserver and mappings

Hey,

I checked back with the Ontoserver team at EHRcon.
We’re allowed to use the openEHR Ontoserver for standards development.
That means we can use it to define our mappings, for example, using ConceptMaps for FHIRconnect.
However, we’re not allowed to use it for running mappings on-site, obviously.

But this still helps us a lot for defining the mappings.
Im however not sure if we should use it in the mapping library since it will require for FHIRconnect users e.g. to have a termserver on side supporting conceptMaps.
Currently mappings are hardcoded as manuals, therefore usable for all.
What is your opinion on that ?

@yampeku @subigre @gandrejc

4 Likes

I think we should go with it. We routinely use ConceptMaps as descriptive artefacts even when clients do not have access to a FHIR TS service.

3 Likes

I think it could be useful to point people to specific mappings. We should probably see a few examples on how people use conceptmaps for openEHR mappings to agree on a common usage (e.g. what’s the system, do we create also the ValueSets, etc.)

3 Likes