Versions Compared

Key

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

...

Place and Date

Ciudad Politécnica de la Innovación
ITACA Assembly Room
Green Cube - Building 8G
Access B - 3rd floor
UNIVERSITAT POLITÈCNICA DE VALÈNCIA

(Details)

- 01 Oct 2019

Participants

Goals

  • Follow-up Terminology Server specification development

Suggestions (by Sebastian Iancu):

  • progress on RM 1.1

  • initiate REST API 1.1

  • review/accept/release ITS JSON and XML Schema

  • SM & conformance testing ?

  • JDT (flat json) ?

  • progress on AQL ?

Agenda

Time

Item

Who

Notes

Remote
Participation

Monday 30 Sep 2019

09:00 - 10:00

Review goals, agenda, previous meeting actions

All

10:00 - 10:15

Governance

Thomas Beale

Component ownership, resignations, general

10:15 - 11:15

Meta review on PRs

Target releases:

Thomas Beale

11:15 - 12:45

REST APIs part 1

Sebastian Iancu

~~~~ L U N C H ~~~~

13:45 - 14:30(?)

RM 1.1.0 CRs

14:30 - 15:30

RM 1.1.0 CRs

all

15:30 - 17:00

PR processing

all

19:30 →

Dinner

Tuesday 01 Oct 2019

09:00 - 10:00

REST APIs

all

10:00 - 11:00

REST APIs

all

11:00 - 11:20

Cistec - short pres

11:20 - 12:15

JSON Data Template

Thomas Beale , all

~~~~ L U N C H ~~~~

13:15 - 14:00

Conformance testing

Pablo Pazos

14:00 - 15:00

Terminology server, mapping tooling, folder for clinical research

Luis Marco-Ruiz

15:00 - 16:00

SEC group calendar for 2019/2020

Bjørn Næss

See below

16:00 - 17:00

openEHR and messaging specifications

ALL

See below

Useful information

https://openehr.atlassian.net/wiki/download/attachments/406749199/openEHR Spain_SEC.pdf?version=1&modificationDate=1567493073441&cacheVersion=1&api=v2

SEC Group “calendar”

The question is: How to perform best as a SEC group?

...

  • We plan for 2-3 physical meetings during one work year (august - June)

  • There will be a regular web-meeting every 3 weeks to track the progress of SEC group activities

  • There will be ad-hoc web-meetings working on specific task within preparing for the next 3-week web-meeting.

openEHR and messaging specifications

Integration with other systems is needed. There is a lot of non-openEHR systems out there. Many hospitals, GP’s, municipalities, regions, countries, etc. has requirements on how to exchange data. These requirements may be local, regional, national and in some situations global based on international standards. Vendors implementing openEHR systems must follow these requirements to compete in the market.

...

The openEHR CDR and clinical models is actually a single source of truth for the clinical data in the EHR for a continuum of care. We should be able to share these data through every messaging specifiation “thrown at us”. It would be for the best for eHealth and not at least the openEHR community if we had a way to define the transformations from the Compositions in the CDR into messaging specifications. Having such a facility we could speed up the implementations of systems and their integrations.

Action items

...

Decisions

  • We agree to have monthly meetings to process tasks and items in between physical SEC meetings
  • The “landing page” for specifications should be improved to make it easier to get newbies into the right specification and/or area of interest
  • Add new category type (for episodes) to COMPOSITION, see: https://openehr.atlassian.net/browse/SPECRM-89
  • Release REST v1.0.1 a.s.a.p., than start on v1.1 and try to correlate with RM 1.1

...