Versions Compared

Key

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

...

Synchronizing alert information between EHR and kjernejournal

...

Gliffy
imageAttachmentIdatt554074122
macroIdcfdf90d4-ed2c-4ba0-80ac-d6c15609b134
baseUrlhttps://kjernejournal.atlassian.net/wiki
displayNameKJ sync alert info
nameKJ sync alert info
diagramAttachmentIdatt554729487
containerId547029232
timestamp1617172277489

...

How to synchronize alert information?

...

Gliffy
imageAttachmentIdatt554729504
macroIde762e67f-a6fe-42b4-9931-1b45a0ecafb2
baseUrlhttps://kjernejournal.atlassian.net/wiki
nameKJ alert info sync table
diagramAttachmentIdatt554729499
containerId547029232
timestamp1617172764762

Manually handling will probably be required when synchronizing data, but this depends on how structured the alert information is registered, and how the local EHR structure maps to the FHIR profiles.
The EHR will normally have a lot of alert information registered. In order to avoid a huge startup task of synchronizing alert information, a good approach may be that healthcare professionals try to synchronizing alert information when they are working with a patient.

...

Display error if download from kjernejournal fails

...

Gliffy
imageAttachmentIdatt554729509
macroId96bd2cae-4b8c-44b7-af77-1a802ac8439f
baseUrlhttps://kjernejournal.atlassian.net/wiki
nameKJ sync alert info download error
diagramAttachmentIdatt553943149
containerId547029232
timestamp1617172400012

Display error if upload fails

...

Gliffy
imageAttachmentIdatt554729545
macroIdcd03a88c-6f4f-419b-a488-89f5c89ba6f5
baseUrlhttps://kjernejournal.atlassian.net/wiki
nameKJ sync alert info error.
diagramAttachmentIdatt554729540
containerId547029232
timestamp1617172595360

Architectural considerations

...