Versions Compared

Key

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

...

  • how should we deal with admin required functionality, e.g. destroy EHR, Compositions, Actors, etc ? Need a specific endpoint /admin or use DELETE action over resources, assuming ACL permits ?

  • delete template is problematic, if is “in use” - but on the other hand this is an admin endpoint, so it should be fine

  • export (and import), later also (partial) extract/ import

    • /admin/ehr/{ehr_id}/export - exports

    • /admin/ehr/import

    • configure the export/import task scope with a payload (e.g. all-ehrs, subset of ehrs based on their ehrIds, “some compositions”)

    • background tasks - consider polling

    • need to define what will be the format for this dump - zip? (Seref:) sqlite? (Severin:) csv or json?

      • we will need to define schema for this export format

      • Ian: see Josh Mandel on dumping ehr-data

      • do we need something

      for
      • like ehr_extract ?

      • self-contained package, including templates, archetypes; maintaining cross references, versioning, contribution

      • import should work on existing populated CDR

        • what if template or other data already exists?

        • Alex: consider keycloak import/export strategies

      • consider flag to anonymize data upon export

    • can be used for data migration from one CDR to another, or another version

  • merging EHRs

  • archiving/shredding Person/EHR (partial, cohort)

  • system?

Bugs

  • Jira Legacy
    serverSystem JIRA
    serverId7788407e-95fd-3d19-96c6-946a2bd486dc
    keySPECITS-60

  • Jira Legacy
    serverSystem JIRA
    serverId7788407e-95fd-3d19-96c6-946a2bd486dc
    keySPECITS-46
    - might be a breaking change

  • Jira Legacy
    serverSystem JIRA
    serverId7788407e-95fd-3d19-96c6-946a2bd486dc
    keySPECITS-44
    but also to other places

  • Jira Legacy
    serverSystem JIRA
    serverId7788407e-95fd-3d19-96c6-946a2bd486dc
    keySPECITS-68

...