Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Same payload as UpdatePatientRequest (/api/v2/patients).  Additional fields to be considered:

Sending RegistryregSend

string

nullable: false

Receiving RegistryregReceive

string

nullable: false

3.5 - Update Registered Patient    

...

Same payload as RegisterPatientRequest.

3.5/6 - Update Patient Status Image Added

Anchor
3.5/6 Update Patient Status
3.5/6 Update Patient Status

UpdatePatientStatusRequest

The updatePatientStatusRequest is used to communicate changes in patient status.

Statuses permitted in EMDIS are PRE, ACT, SUS, STP.  PRE / ACT may have some relevance to Search & Match Service.  SUS / STP may have relevance to Search, Match & Connect.

From EMDIS semantics:

"After the status has been set to suspended (SUS), the transplant centre is fully responsible for pending requests. If a transplant centre is no longer interested in a certain pending request, the request has to be cancelled by the transplant centre by means of a REQ_CAN message. If the transplant centre does not explicitly cancel a pending request, the request will be processed normally by the requested hub.

After the status has been set to stopped (STP), all pending requests but WOR_REQ are cancelled automatically at the remote hub. In this case, no REQ_CAN messages have to be sent by the transplant centre. The only way to reactivate the patient is a PAT_UPD / PAT_STAT message pair. The PAT_UPD is necessary since it cannot be guaranteed that the patient information is still stored at the remote hub. It is up to each hub how long patient information is retained after the search was stopped.

However, it makes no sense to delete a patient who is in workup. Patient searches are sometimes not stopped at remote hubs although the search is not really active any more. This wastes time for matching and gives bad statistics about search length and search counts.

All hubs are strongly encouraged to monitor their international searches closely and stop or suspend them if not longer needed. The searched hub is allowed to send reminder faxes with patients without activities to the patient’s hub."

Fields for consideration:

Sending RegistryregSend

string

nullable: false

Receiving RegistryregReceive

string

nullable: false

WMDA Patient IdentifierwmdaId

integer

nullable: false

Old Patient StatepriorStat

string

nullable: true

New Patient StatenewStat

string

nullable: false

Reason For Changereason

string

nullable: true