21 May 2015 - Meeting Preparation
Problem Report discussion. SEC members: please add new PRs to this table as required, and update Vote / Discussion columns.
...
One of our main goals is to generate CRs that are spread out across the SEC members.
PR | Status | Description | VOTE TO PROGRESS | Priority | PROPOSED ACTION | |||
---|---|---|---|---|---|---|---|---|
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-24 | DEFER | Improving Translation details and other_contributors | TB | Create CR, even though exact details not yet worked out | ||||
Enable content specific flavours of null to be specified per archetype Add a 'reason for null' text attribute in the Reference model | MAJOR | Flavours of Null PRs REQUIRES DISCUSSION | ||||||
DEFER | Minor problem in Iso8601DateTime pattern defintion in XML-Schema | check with SI/Code24 and also Heath/Ocean | ||||||
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 | ||||||
These are all to do with simplifying the 'lower model' of the RM (ITEM_XXX classes) | KA | MAJOR | REQUIRES DISCUSSION Designate one as the main PR, close and reference the two | |||||
Add sibling_id to LOCATABLE so that child objects can be uniquely identified without relying on the name field | MAJOR | REQUIRES DISCUSSION | ||||||
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 | |||||||
language on multiple locations contain invalid ISO 639-1 codes | TB | propose to raise CR that fixes documentation. | ||||||
Definition of DV_ENCAPSULATED is incorrect (SIZE missing) | SI | minor | ||||||
AUDIT_DETAILS.system_id semantics not well defined | minor | REQUIRES DISCUSSION | ||||||
Relax the rule that demands uniqueness of DV_ORDINAL value | minor | REQUIRES DISCUSSION - IAN | ||||||
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. | ||||||
PARTY.reverse_relationships should better be a Set<PARTY_REF> ? | minor | REQUIRES DISCUSSION | ||||||
VERSION commit in XML | minor? | REQUIRES DISCUSSION (Pablo) | ||||||
SPECPR-106 | (see SPECPR-73) | |||||||
Allow creating LINK archetypes to specify queryable links between concepts | MAJOR | REQUIRES DISCUSSION this is the 'contains or references' idea | ||||||
Do not require the @internal@ ontology term descriptions and "name" on instances of internal types | minor | REQUIRES DISCUSSION | ||||||
SPECPR-111 | AUDIT_DETAILS.change_type needs to be empty in CONTRIBUTION.audit | Minor | REQUIRES DISCUSSION | |||||
Use markdown for purpose, use, misuse, etc on archetypes | MAJOR | REQUIRES DISCUSSION | ||||||
Specify ACCESS_ CONTROL_SETTINGS and a concrete subtype | Minor | REQUIRES DISCUSSION (Heath) | ||||||
Allow mapping to terminology for DV_Boolean | Minor | REQUIRES DISCUSSION (Ian M) | ||||||
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) | KA | MAJOR | 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:00 | Informal - get set up with Jira, screens, GTM | ||
11:00 - 11:45 | SEC business
| ||
11:45 - 12:15 | Global review of PRs/CRs
| ||
12:15 - 13:30 | LUNCH | ||
13:30 - 14:00 | Code24 part 1 | ||
14:00 - 15:00 | PR / CR processing | ||
15:00 - 15:15 | Coffee + Shinji / Japan update | ||
15:15 - 16:45 | PR / CR processing | ||
16:45 - 17:00 | break | ||
17:00 - 17:30 | Code24 part 2 | ||
17:30 - 18:00 | PR / CR review | ||
19:00 - | Dinner | ||
Friday | |||
09:00 - 10:15 | Service model / APIs | ||
10:15 - 10:30 | Coffee - Code24 system presentation | ||
10:30 - 11:00 | Query result object | ||
11:00 - 12:15 | PR / CR processing | ||
12:15 - 13:15 | LUNCH | ||
13:15 - 13:30 | Conformance priorities | ||
13:30 - 14:30 | PR / CR processing | ||
14:30 - 14:45 | Coffee | ||
14:45 - 16:00 | specifications wrap-up | ||
drinks? :) |
Issues
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
- EhrScape is starting point
- Agree to update SOAP service definition
- existing defs as starting point
- OWNER: Heath Frankel / TB
- Resources
- Erik's paper: http://www.biomedcentral.com/1472-6947/13/57
- Ian M has a Word doc
- Koray: Amundsen 'collection type'
- 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
...
Canonical Result Set
Marand JSON
Ocean (origina) XML
...