Provider local status handling - 'eligibility'

[jonnyry]

There are a number of local statuses held on the provider system that:

• in some cases affect whether a patient should be accessible via GP Connect
• and in others change the handling of the GP Connect interface

This ticket is to review and ensure we have covered these cases throughout the capabilities.

Depending on whether the guidance deviates for each capability, it may be better to leave the guidance within each capability. If it is broadly the same for each capability, it may be best to create common guidance within the core of the spec.

Local statuses should be considered, such as:

• Patient registration status
  • Active/Registered
  • Inactive/Left
  • Deceased
• Patient registration type
  • GMS/PMS (i.e. standard registration for ongoing GP services)
  • Non GMS/PMS, i.e. Temporary, Emergency, Private etc
• Patient consent/dissent to share
• Patient's record has not been transferred in or is awaiting filing
• NHS number trace status (traced or not traced via PDS or NHAIS)
• Locally stored sensitive flag (this is stored from the last PDS synchronisation)

[jackiebarnes]

For info the Find Patient API currently specifies the returning of an empty bundle for an 'inactive' patient.

This currently also covers the edge case scenarios:

a) Deceased b) 'S-Flagged'

as well as for the Appt Mgmt scenario of a non-active Patient record for the purposes of an appointment, which therefore will trigger the sending of the Register a Patient API to create a temporary registration for an alive, non s-flagged patient.

For both S-Flagged and Deceased patients, given tightened up reqs for Consumer around PDS-alignment - see ticket #391, the request for such patients arriving at the Provider system will be minimal.