On 15/09/2018 22:45, Pablo Pazos wrote:
Thanks Thomas, that in fact seems to generate different nodeIDs for
each analyte, thus avoids the querying issue.
right. The key is that it is done in specialisations - so the querying
in the generic form based on the generic archetypes will still work,
including with LOINC codes. I did not show how to include LOINC codes
directly in the specialisations, but that could be done.
BTW, to be generic is not a requirement on my side, just wanted to
reuse what is published on the CKM, I can create specific archetypes
per panel or analyte, but that approach seems to diverge from the
editor's modeling style. But my idea is the same as yours: try to
distribute pre-built OPTs for specific panels.
I think I need to evaluate the cost of migrating to ADL2 since I see
this as a blocker for 1.4 ADL and OPTs. Also I might need to adopt the
workbench as modeling tools since there is no other tools available
that can be installed easily or is open.
that will be a short term state of affairs - the new Archie tool can
read all these archetypes, but the UI is rough for now (but probably
good enough for a techie like you ;)
Also, the soon-to-be-released Marand ADL-designer Mk2 will (I believe)
have an ADL2 parser added at some stage, since it is AOM2 internally.
- thomas
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
