2022-10-31 SEC Call notes

10 min

Opening

USEFUL Jira RESOURCE: CRs I have not accepted.

SEC Jira board.

30 min

REST API update

@Sebastian Iancu

OpenAPI Strategy

• https://discourse.openehr.org/t/open-api-strategy/2668

• API Blueprint => OpenApi

Overview for REST API work to be done - for Release 1.1.0 or 2.0.0

Progress:

• some progress on tests

• test 11 - some code generation output now compiling C#, Groovy, Dart… (many more)

• test 12 - validation; checks using mock server

• made adjustments to JSON schemas based on test runs;

Need to make _type field optionality settable.

30 min

JSON schema update

@Pablo Pazos

Working on 2 versions of schemas -

• canonical one

• relaxed one for API

New Github issue ITS-JSON #14

@Pieter Bos Very nice work Pablo! I did a quick scan, and I see four categories of changes:

1. entry points, I can add these to the generator

2. small problems in the BMM, we can fix them in the BMM and regenerate

3. Some discussion points about whether we should change some things

4. inconsistencies between base and rm spec - the bmms use base! These are mainly classes used in the AOM, and we need to check actual implementations instead of fixing them to the RM spec I think

Chase up semantics of ACCESS_SETTINGs in RM.

15 mins

Links in archetypes

@Thomas Beale

See Discourse post.

@Ian McNicoll - make it look like Entry → Entry ‘containment’ view; BMI example; prefer ENTRY attribute; will be difficult to specify in advance what the target looks like

@Erik Sundvall

• Think about what version of target is pointed to - a specific version or the entire versioned object (meaning pointing to the latest version?) Likely Both kinds should be allowed.

• Also be clear about at what timepoint(s) constraint/link/citation checking is expected to be done by the application/CDR. Llikely only during construction and storage of the COMPOSITION citing the the target).

@Diego Boscá Tomás - use rules - consider what it looks like in rules.

@Erik Sundvall point to an inner path, e.g. Weight: Real value.

@Pablo Pazos How is the runtime ref actually created, and how does the constraint help the data builder do it?

Link target may already exist; may be in same Contribution (BMI example - can be done either way).

@Thomas Beale : don’t see how Entry ‘virtual attribute’ will work.

AQL querying should work the same, regardless of what the (say) BMI structure is. Need to work out link following, also Folder ‘containment’ in AQL generally.

@Ian McNicoll nested problem lists - e.g. ‘related problem’

Other example - point to lab analyte CLUSTER, e.g. by fixing LOINC code in the constraint.

Reports - solvable as well by this approach.

@Joost Holslag on the second topic, that get’s mixed in: one of my thoughts is how to model an instruction to measure a blood pressure. to me it feels strange that many fields from the obs (device, position, location etc). can also be relevant in the intstruction: You have to measure the blood pressure using the philips device, with the patient laying down. So to me it doesn’t make sense to model those fields twice. I was thinking don’t model elements in entries, but always in clusters. And use_archetype those clusters in the instruction and the observation.

@Ian McNicoll - I have had similar thoughts about the opposite i.e use fragments of entries as if they were clusters - let's discuss.

@Joost Holslag yeah, I’ve had that thought too: Use_archetype observation.blood_pressure.device

@Diego Boscá Tomás what about instruction state machine - constraint the states you can go from other state
@Ian McNicoll = yes - split out ISM as a pluggable structure!!

10 mins

Entity model - resources, parties, assets.

@Thomas Beale

See draft.

Outstanding topics:

• HighMed - FHIR bridge - put back to Q2 2023

Agenda items:

• API for EHR Extracts

•