To be able to export the FHIR Logical Models, as mention in issue #19 to UML. We need a convertor FML -> zib UML.
the UML should be enterprise architect 14 compliant .xmi. It should also conform to iso13972 (e.g. for data types and terminology binding). And some more constraints may be documented here: documentation about the zib UML structure: https://zibs.nl/wiki/Documentatie_Klinische_Bouwsteen
The conversion algorithm must be implementable by a 3rd party app like ckm or zibs.nl and potentially ‘art decor’.
The algorithm should be open source. Or at the very least if not the actual code enough information should be available for others so they can create a similar algorithm that produces ‘identical’ results.
we decide against exporting to FLM because it adds complexity, and FLMs are so unstructured it's still hard to build a reliable processor to go further on the chain.
To be able to export the FHIR Logical Models, as mention in issue #19 to UML. We need a convertor FML -> zib UML. the UML should be enterprise architect 14 compliant .xmi. It should also conform to iso13972 (e.g. for data types and terminology binding). And some more constraints may be documented here: documentation about the zib UML structure: https://zibs.nl/wiki/Documentatie_Klinische_Bouwsteen
The conversion algorithm must be implementable by a 3rd party app like ckm or zibs.nl and potentially ‘art decor’. The algorithm should be open source. Or at the very least if not the actual code enough information should be available for others so they can create a similar algorithm that produces ‘identical’ results.