search

scandihealth / lpr3-docs

https://scandihealth.github.io/lpr3-docs/
MIT License
11 stars 7 forks source link

Problem with timestamp #192

Closed kbhCGI closed 6 years ago

kbhCGI commented 6 years ago

Hi

We get this error. image Is the problem that we have a timestamp in the message, that is after the timestampe on your machine. ex. my machine 10:00:00, you machine 09:59:58

TueCN commented 6 years ago

This is rule 00.01 in Logisk datamodel og indberetningsregler - Bilag 1 (PDF)

The problem it seems is that the Slutdato value of the patient's bopæl is in the future.

Note: Rule 00.01 also validates that all timestamps lie before indberetningens tidsstempel which is defined as:

En given LPR3-indberetnings tidsstempel skal oplyse, hvornår selve indberetningen er genereret af fødesystemet. Dette er ikke det samme tidspunkt som selve indsendelsen/transmissionen af indberetningen, der altid - også i et online-indberetningsmiljø - vil ligge efter tidspunktet for generering

indberetningens tidsstempel is thus the effectiveTime value of the CDA ClinicalDocument element. This value is not currently visible on the UI (it is used in validation and stored in the database).

This means you must make sure the ClinicalDocument's effectiveTime timestamp is chronologically after all other timestamps in the submission, but not in the future.

TueCN commented 6 years ago

RESOLUTION Currently both startdato (hl7:low) and slutdato (hl7:high) are mandatory when a hl7:usablePeriod element is provided on the hl7:addr element. We have just discussed this internally and decided to make both timestamps optional.

The art-decor template has been updated and this change will go into effect with the next deploy.