We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For one of the labs we are testing with, we notice that the versionId they provide in the diagnosticReport is a timestamp
<DiagnosticReport> <id value="Report-2409137941" /> <meta> <versionId value="2024091315171535" /> <profile value="https://www.ehealth.fgov.be/standards/fhir/lab/StructureDefinition/be-laboratory-report" /> </meta>
As of now we fail on this versionId because we expect (sequential) integers and not a timestamp. Can a timestamp be used as versionId?
The text was updated successfully, but these errors were encountered:
@bdc-ehealth would it be possible to have a look at this one?
Sorry, something went wrong.
@tomdebacker-corilus
Hi Tom, the answer you need is here: https://hl7.org/fhir/R4/resource.html#Meta:~:text=Usage-,versionId,-(0..1) , see the Usage column in particular. I fear the answer is 'yes'.
Hello, if this is to be supported, can it be added is a testcase on the testserver ? Or at least, can you provide an example test file here.
No branches or pull requests
For one of the labs we are testing with, we notice that the versionId they provide in the diagnosticReport is a timestamp
As of now we fail on this versionId because we expect (sequential) integers and not a timestamp.
Can a timestamp be used as versionId?
The text was updated successfully, but these errors were encountered: