You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The expression in constraint 'app-4' for Appointment uses 'no-show' instead of 'noshow' which make it useless since there is no status 'no-show'.
Environment
Using LinuxForHealth FHIR Server 5.1.1.
To Reproduce
Steps to reproduce the behavior:
Create a request to Appointment and use 'noshow' as the status and add a cancellation reason.
e.g.
See the error message in the response body. { "severity": "error", "code": "invariant", "details": { "text": "app-4: Cancelation reason is only used for appointments that have been cancelled, or no-show" }, "expression": [ "Appointment" ] }
4- Using 'no-show' will be rejected as well because the status code is 'noshow'.
Expected behavior
The request should be accepted since it doesn't violate the rule.
Additional context
This could be solved easily by removing the dash from the expression part of the constraint, as in the pull request.
The text was updated successfully, but these errors were encountered:
It looks like that was reported to HL7 at https://jira.hl7.org/browse/FHIR-37896 and they already fixed it for R5.
I think it would be reasonable to back-port that fix for our R4B implementation.
Describe the bug
The expression in constraint 'app-4' for Appointment uses 'no-show' instead of 'noshow' which make it useless since there is no status 'no-show'.
Environment
Using LinuxForHealth FHIR Server 5.1.1.
To Reproduce
Steps to reproduce the behavior:
e.g.
{ "severity": "error", "code": "invariant", "details": { "text": "app-4: Cancelation reason is only used for appointments that have been cancelled, or no-show" }, "expression": [ "Appointment" ] }
4- Using 'no-show' will be rejected as well because the status code is 'noshow'.
Expected behavior
The request should be accepted since it doesn't violate the rule.
Additional context
This could be solved easily by removing the dash from the expression part of the constraint, as in the pull request.
The text was updated successfully, but these errors were encountered: