Hi Heather,
I don’t know the ideal way to link this information, this was in fact my question. I see several directions but no ideal way yet.
- change the rectal bleeding element to (add a) DV_EHR_URI that will store the link to the rectal bleeding element in Examination of faeces. Then implementers will have to build the logic to resolve this information when rendering. But to do that the automatically, the DV_EHR_URI needs to contain a regex to constrain it to only link to that element (like we do with use_archetype).
- we could build an aql query that resolves the info at the Examination of faeces rectal bleeding element. But how do we store an aql query in an archetype? rules could work but doesn’t at the moment.
- we could rebuild this archetype and replace the element with the cluster, but that would add superfluous information, that can only be hidden in a template(overlay).
- we could use annotations section of this observation archetype to specify the linked information, but to make this computable we would need a specification for this type of information. And it doesn’t feel like the right place.
Any other thoughts?