Re: Generic modeling and issues for querying

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

Re: Generic modeling and issues for querying

Thanks Thomas, that in fact seems to generate different nodeIDs for each analyte, thus avoids the querying issue. 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

Re: Generic modeling and issues for querying

Pablo, I have also seen a need for queries that distinguish analyte level objects, within the new lab archetypes. The original reason was to be able to distribute pre-built panel templates (or even archetypes) to EMR (=PEP) locations in Brasil, but your need is generic. This wiki page

Generic modeling and issues for querying

Hi all, Lately I've been working a lot with lab test reports. Current CKM modeling for this relies on a generic model that applies to any kind and structure of result in this way: - COMPO.report-result // any result document - OBSERVATION.laboratory_test_result// results container, can

Re: What's the correct XML in an OPT for multiple terminology references?

Just remembered children of attribute can handle multiple alternatives, while this is syntactically correct I'm not sure if the alternatives can be of the same object type: defining_code

What's the correct XML in an OPT for multiple terminology references?

Hi, I'm having trouble generating OPTs (1.4) from archetypes that reference multiple terminologies from a DV_CODED_TEXT. For instance, I have a coded node that will be coded by LOINC or SNOMED-CT, that can be set in the archetype. But when exporting the OPT from the Template Designer, only LOINC