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
After reviewing the specifications of R4, we identified some shortcomings related to our use cases. First, we feel the need for a status like "ended," which is available in R5.
Secondly, we require a timestamp indicating when the status was changed. In R5, we found the "statusChanged" feature, which meets our requirements. This is essential for sorting the list of prescriptions and providing this information to the executors or prescribers.
What would be our best way forward from here, considering we currently have to stay on R4?
The text was updated successfully, but these errors were encountered:
We can support the following statuses and reasons:
"expired" means status = cancelled, statusReason = "expired"
"manually cancelled" means status = cancelled, statusReason = "revoked"
For this reason, we decide:
a) we do not need the status "ended" in R4, since our needs are met with status and statusReason as above
b) we will preadopt the statusChanged element from R5 into an extension to our R4 resource profile. This is pending with business updating the functional specs
After reviewing the specifications of R4, we identified some shortcomings related to our use cases. First, we feel the need for a status like "ended," which is available in R5.
Secondly, we require a timestamp indicating when the status was changed. In R5, we found the "statusChanged" feature, which meets our requirements. This is essential for sorting the list of prescriptions and providing this information to the executors or prescribers.
What would be our best way forward from here, considering we currently have to stay on R4?
The text was updated successfully, but these errors were encountered: