Skip to content

Isolations- und Quarantäneverordnung nicht aktualisieren #1276

@St-Annette

Description

@St-Annette

Is your feature request related to a problem? Please describe.

Bisher werden die Isolations- und Quarantäneverordnungen immer wieder aktualisiert und auch rückwirkend auf schon abgeschlossene Fälle angewandt.
Veränderungen in den Bestätigungen sollten sich nur auswirken auf alle Fälle ab dem Zeitpunkt wo die Dokumente aktualisiert worden sind (nicht rückwirkend für Dokumente).

Außerdem sollten alle vergangenen Dokumente so wieder in das System eingepflegt werden, so dass die Bestätigungen so aussehen, wie sie für den verordneten Zeitraum aktuell gewesen sind.

Describe the solution you'd like

Process

  • To request changes to documents, the following data is required in the future:
    • Changed Document Version
    • Diff of changes (for example an annotated PDF)
    • Separate Text File for Text (for copy/paste which does not work well with PDF)
    • Decide if updating the current version or creating a new one

Setup

To be able to test documents, a new flow is needed to add the documents that support:

  • testing
  • export of all documents/versions via CI for the change process
  • adding elixir modules to polyfill old behavior to avoid BC breaks

tasks:

  • Hygeia Application scans template directory for modules and loads them on start
  • Hygeia Application scans template directory for tests and loads them into ExUnit
  • Private Repo contains a CI that tests the documents and exposes them as artifacts

Document Cleanup

  • Layouts are extracted from documents
  • Code is cleaned up
  • Blocks of text are extracted into markdown
  • Info Links at the end of the document are saved as markdown on tenant and are included dynamically
    • can also be shown on the person overview page
    • can also be removed from doc entirely and only be shown on the person overview page

Data Model

  • Each Phase contains a document date (default = creation date)
  • Document date can be changed to get newer / older docs
  • When migrating, the document date is set to coalesce(phase.end, phase.inserted_at)

Versioning

  • Specify Config Format to define which document version is used for a given date
  • Correct Document is loaded given a date
  • The current document and 3 older versions of documents are created to capture past quarantine/isolation lengths
    • ⚠️ This is not an exact document from the past, we're lacking information to do that properly.

Describe alternatives you've considered

  • Store Parameters for the document generation and only the current document version can be changed.
    • is not flexible enough for past changes and therefore probably not the right solution

Additional context

References

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions