Content Comparison

10 min

Intro

15 min

REST API Status

Discuss today:

• review Overview for REST API work to be done - for Release 1.1.0 or 2.0.0 , analyse missing goals, evaluate breaking changes
  Alex Vidrean will ask internally for a impact on EHRbase on adoption on a v2

• we should mention the future plans to have /registry working with future demographics (entity)

• we should publish incremental drafts on github pages

• we should also update and keep in sync downstream dependent specs: SM, conformance specs and tests, postman collection

  • Pablo Pazos: I am working on a groovy implementation (using Spock framework) that replaces the robot-tests and is also checking also the process (from conformance perspective)

10 min

SMART on openEHR

decided to publish draft https://openehr.github.io/specifications-ITS-REST/smart_app_launch.html for review (on discourse public section)

Flat format specification

Discussed last time:

• Ian: encourage REST API implementors to support flat-format if they want to support) on official endpoints

• Alex: also the /example endpoints

• Ian: flat format format should become ‘official’ specification - todo: include https://github.com/better-care/web-template/tree/master

• Erik: v0.1 could be equivalent to the open source Java/Kotlin code (the code is the documentation), v0.2+ should be a new formal spec

Eventing specs

Discussed last time:

• work on google docs,

• meet in within this WG and offline

• Seref: make new spec: Event Model sibling of Service Model

Ian’s Postman collection

Discussed last time:

• adopt Postman collection