DV_EHR_URI

SI, MP

• MP: consider deprecating DV_EHR_URI; register ‘ehr’ scheme and just use DV_URI; why limit URIs to anything specific? Also would have to relax LINK URI link constraint

• TB: question on being able to specify target of links in ADL tools - currently hard.

• We’ll discuss this again next meeting with Erik Sundvall

Integration package

Diego

Waiting on SEC progress.

Simplified data formats

TB

Birger: Better platform - ctx.xxx shortcuts - need to document mappings / rules.

Stefan Spiska: ? consider ‘ctx’ defaults approach for canonical format.

Ian - problem of asymmetry of input / output - output contains ‘defaulted fields’ populated, and no ctx block. This seems complex to new devs.

Matija: (some) missing ctx fields populated by back-end.

Birger: input JSON for e.g. a BP can be very lean with ctx and server-side defaults.

Ian: radical idea: ?store the ctx block with the COMPOSITION.

Birger: no real problems in Highmed. Would like to standardise nicely for EhrBase as well… - mainly a question of good documentation.

Pieter: Q on disambiguation of types, e.g. Event sub-types.

TB: JSON ‘enhanced’ parsing approach for leaf types should be ok.

SI: use archetype +/- RM to determine in some circumstances

And a bit of special processing for types that can’t be inferred.

Application retrieve data sets

TB

Ref: wiki page.