search

SevKohler / OMOCL

Apache License 2.0
5 stars 2 forks source link

Add identifier to yaml #8

Open joostholslag opened 3 months ago

joostholslag commented 3 months ago

I think it would be helpful to add a human readable identifier to the yaml mapping file, of the mapping itself, not just the archetype. The identifier should also be versioned. If this spec will (potentially) be part of the openEHR specification, I suggest adopting the openEHR resource model https://specifications.openehr.org/releases/BASE/latest/resource.html#_authored_resource_class. Alternatively you could adopt the FHIR canonical resource, which will be more familiar to people familiar with fhir. https://build.fhir.org/canonicalresource.html#CanonicalResource

SevKohler commented 3 months ago

@yampeku what do you think about that. I would say with the archetype + the version of the mapping provided with the new FHIRconnect+OMOCL header its maybe enough as an identifier ?

Problem will be more colliding mappings for the same archetype.

yampeku commented 3 months ago

I can see that being useful, as maybe several mappings could coexist in the future (e.g. conditions coming from different sources that you want to specify types)

joostholslag commented 3 months ago

Yes. And you want some name spacing. There will be many mappings for the same archetype. The ckm one should be authoritive. But how will you know which one is from ckm.