Versions Compared

Old Version 59

changes.mady.by.user Erik Sundvall

Saved on

compared with

New Version 60

changes.mady.by.user Thomas Beale

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

21 May 2015 - Meeting Preparation

Problem Report discussion. SEC members: please add new PRs to this table as required, and update Vote / Discussion columns.

...

PRStatusDescriptionVOTE TO
PROGRESS 		PriorityPROPOSED ACTION

SPECPR-11

DEFER Need to specify a choice of different objects within a container attribute in Archetype and Template  

Group construct - put off till AOM 2.1

SPECPR-24DEFERImproving Translation details and other_contributorsTB Create CR, even though exact details not yet worked out

SPECPR-41

SPECPR-62

SPECPR-119

 

Enable content specific flavours of null to be specified per archetype

Add a 'reason for null' text attribute in the Reference model

CLUSTER also needs a Null_flavour

 MAJOR

Flavours of Null PRs

REQUIRES DISCUSSION

SPECPR-43

DEFERMinor problem in Iso8601DateTime pattern defintion in XML-Schema  check with SI/Code24 and also Heath/Ocean

SPECPR-70

 Simplify modelling of 'CodedWithExtensions' CWE pattern of DV_CODED_TEXT by addition of an 'unbounded' qualifier to defining_code constraint MAJOR

REQUIRES DISCUSSION

The CWE question

SPECPR-73

SPECPR-74

SPECPR-106

 These are all to do with simplifying the 'lower model' of the RM (ITEM_XXX classes)KAMAJOR

REQUIRES DISCUSSION

Designate one as the main PR, close and reference the two
others, and create a single CR in the RM component (exact
change unknown so far)

SPECPR-91

 Add sibling_id to LOCATABLE so that child objects can be uniquely identified without relying on the name field MAJORREQUIRES DISCUSSION

SPECPR-94

 AOM node_id optionality rules not clear  propose: raise CR to rectify invariant to be optional in ADL 1.5; then in ADL 1.6 or ADL 1.7, bring in mandatory node_ids as per ADL 2

SPECPR-95

 language on multiple locations contain invalid ISO 639-1 codesTB propose to raise CR that fixes documentation.

SPECPR-98

 Definition of DV_ENCAPSULATED is incorrect (SIZE missing)SIminor 

SPECPR-99

 AUDIT_DETAILS.system_id‏ semantics not well defined minorREQUIRES DISCUSSION

SPECPR-101

 Relax the rule that demands uniqueness of DV_ORDINAL value minorREQUIRES DISCUSSION - IAN

SPECPR-103

 Add instance level annotations capability to RM MAJOR

REQUIRES DISCUSSION

TB: This is a variation on a common request; my view is that it has to be done with referencing and that doing it properly requires new RM.

SPECPR-104

 PARTY.reverse_relationships should better be a Set<PARTY_REF> ? minorREQUIRES DISCUSSION

SPECPR-105

 VERSION commit in XML minor?REQUIRES DISCUSSION (Pablo)
SPECPR-106 (see SPECPR-73)   

SPECPR-107

 

Allow creating LINK archetypes to specify queryable links between concepts

 MAJOR

REQUIRES DISCUSSION

this is the 'contains or references' idea

SPECPR-109

 Do not require the @internal@ ontology term descriptions and "name" on instances of internal types minorREQUIRES DISCUSSION
SPECPR-111 AUDIT_DETAILS.change_type needs to be empty in CONTRIBUTION.audit MinorREQUIRES DISCUSSION

SPECPR-114

 Use markdown for purpose, use, misuse, etc on archetypes MAJORREQUIRES DISCUSSION

SPECPR-115

 Specify ACCESS_ CONTROL_SETTINGS and a concrete subtype MinorREQUIRES DISCUSSION (Heath)

SPECPR-116

 Allow mapping to terminology for DV_Boolean MinorREQUIRES DISCUSSION (Ian M)

SPECPR-117

 Support newlines and formatted in DV_TEXT MAJOR

REQUIRES DISCUSSION (all)

This is the recurring issue of DV_TEXT formatting

SPECPR-118 Support Clinical Finding pattern in RM (negation / absence / presence)KAMAJOR

Help reduce unnecessary clutter and improve modelling

REQUIRES DISCUSSION

need something in RM? - Ian - create wiki page

  

Template Data Schema?

TDO

   

 


Agenda

 

Thursday 
10:00 - 11:00Informal - get set up with Jira, screens, GTM
11:00 - 11:45SEC business
  • introduction
    • SEC governance
  • goals of meeting
    • PR -> CR conversion
    • define & assign releases
    • share the work
  • the documentation situation
11:45 - 12:15Global review of PRs/CRs
  • Review releases of components
  • triage out: actionable / need discussion / defer
12:15 - 13:30LUNCH
13:30 - 14:00Code24 part 1
14:00 - 15:00PR / CR processing
15:00 - 15:15Coffee + Shinji / Japan update
15:15 - 16:45PR / CR processing
16:45 - 17:00break
17:00 - 17:30Code24 part 2
17:30 - 18:00PR / CR review
19:00 -Dinner
  
Friday 
09:00 - 10:15Service model / APIs
10:15 - 10:30Coffee - Code24 system presentation
10:30 - 11:00Query result object
11:00 - 12:15PR / CR processing
12:15 - 13:15LUNCH
13:15 - 13:30Conformance priorities
13:30 - 14:30PR / CR processing
14:30 - 14:45Coffee
14:45 - 16:00specifications wrap-up
 drinks? :)

Issues

Sebastian Iancu: UML
Release packages - issue of syncing releases of components e.g. RM and XSDs - needs dependency model like apt-get /RPMs/Maven/Ruby gems etc - e.g. Maven requires >= versionX 

Actions

  • UML/tooling etc - TB / Bostjan

APIs and Service Model discussion

Data services

  • Agree on priority to publish REST-based data service specification (EHR, demographics, EHR Index, access control...)
    • EhrScape is starting point
      • confirm no IP problem to convert to spec
    • OWNER: Bostjan Lah
  • Agree to update SOAP service definition
    • existing defs as starting point
    • OWNER: Heath Frankel / TB
  • Resources
  • Technical issues:
    • don't include anything to do with sessions in REST API - single-shot commits; treat session as a specific local SSO/auth problem

Business Services

E.g. Shared Care Plan, Shared Meds list etc

Application services

Content-generated FHIR-like resources - archetype- or template-based.

...

Can defined pre-defined query sets for given FHIR resource.

Canonical Result Set

Marand JSON

Ocean (origina) XML

...