Page Comparison

...

overall

• Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-58

  • it supporting flat and json/xml, controlling with Accept header

  • /definition/adl1.4/{templateId}/example[?type={filterType}&detailLevel={detailLevel}]

    • filterType = input|output

  • it contains a larger set of data, but not necessary the largest, given values for some optional fields

    • detailLevel = min|medium|max

  • can be used for validation and developments

• Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-35

...

• Add /ehr/{ehr_id}/folder and /ehr/{ehr_id}/versioned_folder

  Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-63

• Add missing EHR_ACCESS ?

  • similar to EHR_STATUS

  • we will mention in specs that this resource is created automatically by the system when the EHR is created, and is not possible to add it in the payload of EHR creation (like we do for EHR_STATUS)

• fix EHR summary - not “very” restful => this is a breaking change

Definitions

• Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-43

  => admin?

• should we support also archetypes? => no, or at least is low prio, perhaps next version

• are we going to support (reading) terminology / value sets? => no, this is the job of terminology service

• add alternative /definition/adl2/{archetype_id_matcher} and deprecate /definition/adl2/{template_id}/{version_pattern} - potentially breaking change

• query type => add “formalism” in text

...

see also Pablo’s proposal

...

Bugs

• Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-60

• Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-46

  - might be a breaking change

• Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-44

  but also to other places

• Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-68

...

• Audit headers with JSON Simplified Format

  Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-64

• converting location response header to content-location (see https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Location ) => breaking change

  • Pablo: an idea to backport functionality from v2 to v1 but do it with right headers, we should actually deprecate the “wrong” headers and already add the new-future headers

Missing (specification) details

• Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-62

• Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-61

• Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-50

  try with prefer=identifiers

• Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-48

  discussed on discourse, we should allow it (todo check), no need to do anything on REST level

...

• Reformat Introduction

• Conformance info

• IANA

  Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-39

• Reformat and reorganize

  Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-36

• Overall Layout

• sync with SM, add UV models (relaxed RM)

  Jira Legacy
  server System JIRAJira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-34

• authentication endpoint => (still) no needed

• audit service endpoint => not prio, perhaps not part of rest api

• (cds) hooks => if Cambio can help with a proposal then it can be included, but we should also look into generalized triggers

• simplify, consolidate and reuse yaml-blocks while building up specs

...