search

nhsconnect / gpconnect

GP Connect API specification
https://digital.nhs.uk/services/gp-connect/gp-connect-specifications-for-developers
Apache License 2.0
34 stars 26 forks source link

MedRequest.status definition #1058

Open PeteSalis opened 3 years ago

PeteSalis commented 3 years ago

Is the way that TPP have implemented this field correct?

Is our spec correct. This field should be the status of the medication order and not a reflection of whether the patient is taking the medication.

PeteSalis commented 3 years ago

Also check the consumer guidance.

martinhillyard commented 3 years ago

Consumer data may need to be updated. Needs to be checked along with the guidance.

PeteSalis commented 3 years ago

Discussed with Martin.

We agree that for Med Request status where the intent is order it should not be active.

Where the intent is plan it is complete once all the authorised issues have been made or the authorisationExpiryDate has been reached. For repeat dispense once the issues have been made then the plan is complete

I will write the new versionof the MedRequest.status

For Medication Statement we agreed that we need to run the FHIR definition past the clinicians.

This could be used to carry the status from the system. This would mean this field in GP Connect is populated inconsistently as that is the behaviour in the GP estate. If we followed the exact FHIR definition it would give consumers the option of using the more consistent MedRequest.status or the variable MedStatement.status. Is this desirable or will it just be more confusing for consuming systems?

martinhillyard commented 2 years ago

Change applied. Release note required

martinhillyard commented 2 years ago

Typo for completed code needs to be changed

martinhillyard commented 1 year ago

Changes don't seem to have not been merged into 1.6.2 as yet. Fix version needs to be updated according to where these changes will be applied or issue closed if the changes are not going to be made.