...
Synchronizing alert information between EHR and kjernejournal
...
Gliffy |
---|
imageAttachmentId | att554074122 |
---|
macroId | cfdf90d4-ed2c-4ba0-80ac-d6c15609b134 |
---|
baseUrl | https://kjernejournal.atlassian.net/wiki |
---|
displayName | KJ sync alert info |
---|
name | KJ sync alert info |
---|
diagramAttachmentId | att554729487 |
---|
containerId | 547029232 |
---|
timestamp | 1617172277489 |
---|
|
...
How to synchronize alert information?
...
Gliffy |
---|
imageAttachmentId | att554729504 |
---|
macroId | e762e67f-a6fe-42b4-9931-1b45a0ecafb2 |
---|
baseUrl | https://kjernejournal.atlassian.net/wiki |
---|
name | KJ alert info sync table |
---|
diagramAttachmentId | att554729499 |
---|
containerId | 547029232 |
---|
timestamp | 1617172764762 |
---|
|
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 |
---|
imageAttachmentId | att554729509 |
---|
macroId | 96bd2cae-4b8c-44b7-af77-1a802ac8439f |
---|
baseUrl | https://kjernejournal.atlassian.net/wiki |
---|
name | KJ sync alert info download error |
---|
diagramAttachmentId | att553943149 |
---|
containerId | 547029232 |
---|
timestamp | 1617172400012 |
---|
|
Display error if upload fails
...
Gliffy |
---|
imageAttachmentId | att554729545 |
---|
macroId | cd03a88c-6f4f-419b-a488-89f5c89ba6f5 |
---|
baseUrl | https://kjernejournal.atlassian.net/wiki |
---|
name | KJ sync alert info error. |
---|
diagramAttachmentId | att554729540 |
---|
containerId | 547029232 |
---|
timestamp | 1617172595360 |
---|
|
Architectural considerations
...