Page Comparison

...

• Jira Legacy
  server System Jira 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 Jira serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECITS-35

• serializing errors:

  • investigate if RFC is in use -https://datatracker.ietf.org/doc/html/rfc7807 (https://github.com/zalando/problem is also using it)

  • try to align if possible with FHIR

  • we should not use RM type

EHR

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

  Jira Legacy
  server System Jira 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

...