HSC Unknown Service

From CCMDB Wiki
Revision as of 13:29, 2020 January 30 by Ttenbergen (talk | contribs)
Jump to navigation Jump to search

This page is about the "Unknown Service" that has showed up for Medicine at HSC around

When did this start?
  • SMW


  • Cargo


  • Categories

, and how we collect this.

Background

Patients on contingency beds sometimes are not assigned a service and show up as "unknown service" in EPR. Sometimes EPR eventually gets updated with the service looking after the patient, but sometimes patients remain under "unknown service" even until they get discharged.

Collection process

Patients that show up on EPR Reports as "unknown service" are currently divided up by the HSC Medicine collectors and laptops.

If they are assigned to a service before collection starts, they are collected on that eventual Service/Location's laptop. Boarding Loc is entered if appropriate.

If they remain "unknown service" for some time, collection is eventually started on a laptop, with these patients being "shared" by the HSC Medicine collectors.

  • How are they shared? E.g. what list do they come from, and how do you decide who takes which one?
  • SMW


  • Cargo


  • Categories

Improving how we handle patients eventually assigned to a service

If an "unknown service" patient's data collection is started on one laptop, and they are eventually assigned to the ward collected on a different laptop, then our current setup does not allow us to change the Service/Location to that.

Collectors were asking if it’s possible to have other units (A4, D4 & H4) added to the drop down option of Service/Location. Currently, this would mean collectors need to confirm with each other with Pat ID/Serial number to use, since our D_ID is unique only if site and serial combined are unique. So, adding these options to the dropdown would risk overwriting another patient's data on Centralized.

This problem has been identified for other reasons, see Update of D ID to include a laptop identifier. Ideally, this needs to be implemented, at which point solving this issue will become trivial.

The issue was discussed at Task Meeting 2020-01-29 and deferred to more discussion.

Related articles

Related articles: