Storing codes of two external terminologies

Specifications Terminology
13

Here comes my bull in a china shop moment :grin: :

Using the mappings of DV_TEXT, one can indeed store N mappings with references to various terminologies as @siljelb says. However, I cannot see a way to constraint what those terminologies are allowed to be. I.e. you can record mappings to terminologies, but you cannot force validation to reject data if it contains a mapping to a code from SuperDuperAstrologyChartBasedCodingSystem©

You can record the fact that a value must be from a particular terminology, and its subset etc, if you go with DV_CODED_TEXT as @damoca mentions, and that can be expressed at the archetype level.

So if you want to make the terminology of the mapping part of validation, use DV_CODED_TEXT in your archetype, or specialise DV_TEXT fields of the archetype you’re re-using to DV_CODED_TEXT in a template.

If you’re ok with users using any terminology, which means you’ll only query for the ones you’re interested in when using the data, and not be concerned about codes from terminologies you don’t care about, then stay with DV_TEXT.

Can I join the clinical modelling experts group now? :grin: ? I’d be very happy to be educated if the above is wrong.

4 Likes