2020-05-18 SEC call notes

RM 1.1.0

current state of 1.1.0 CRs

TB to progress tags minimal form documentation

‘incomplete’ content and relaxed validation

General agreement to proceed

DV_URI

Need to progress further

AQL 1.0.1

6 CRs in Review

1 CR outstanding for 1.0.1 - SPECQUERY-20: Clarify major keyword documentation and semantics

• Time window - can we obsolete in AQL 1.0.1?

ADL2

• 24 issues in 2.1.0 1;

• 10 in review

• C_TERMINOLOGY_CODE strength CR - will go ahead (discussion)

• either add DV_PLAIN_TEXT 1 to RM or frozen in AOM2

@pieterbos, @thomas.beale, @borut.fabjan, @sebastian.garde …

• Solve direct representation of external codes in data and/or in AOM2

@ian.mcnicoll

• possible change: allow free use of specialised at-codes to create local subordinate codes in archetype

• want a ‘human name’ field sometimes on Templates, and even occasionally on archetypes; could potentially be implemented as id1.description . Otherwise… still needs translations, therefore needs to be a term.

@ian.mcnicoll

• Some codes (id-codes in ADL2) are design-only e.g. Archetype slot codes; do we want a kind of code or meta-data item that marks codes as ‘design only’.

@ian.mcnicoll

• Nedap keeps Archetype slot codes in the root Locatable node in data - need to discuss this more widely.

@pieterbos

REST APIs

Status

• JSON schema - discussions needed

• sync with RM 1.1.0

(@sebastian.iancu restarting in June)

Terminology services interface - default = FHIR-ish wrapper; see Highmed work - ‘drivers’ - e.g. bind to FHIR, Ocean, Better etc; main utility - indicate result set structure. Inclusion of relationships - local issue. See Luis’ wiki page.