I also concur with Bert that if CKM were to develop into what is intended
to be, the FHIR mapping problem can cease to be a major concern for
majority of the use cases.
Could we not look at extending term mapping in OpenEHR to cover this
requirement also? That way nodes in archetypes can be
In fact is this a bit of exciting question. On one side, the OpenEhr
community has the point of view that OpenEhr is static, CKM rules and is
planned to cover the whole information requirement for healthcare. Do not
invent your own archetypes, but use the high quality CKM archetypes is an
advice I
I also did some mapping work FHIR -> openEHR using Mirth, but this is
ad-hoc, no automatic mapping yet, for that you need to define a lot of
constraints to make it work automatically. Maybe some semi-automatic tool
come out in the future, assisting architects on doing such mappings, either
way
3 matches
Mail list logo