Move a patient from one facility to another

Technical Support Development
1

Hello community

How can i move a patient from one facility to another?, if the contact edit form does not have the option Would you like to move them to another place?* ie

Screenshot 2024-08-28 at 3.31.54 PM
Screenshot 2024-08-28 at 3.31.54 PM1558×706 61.2 KB

@jkuester

2

Due to the way that contacts/reports contain denormalized data about their parent hierarchy, it is recommended to use the cht-conf move-contacts action to move contacts around. The downside of this, of course, is that it is an admin-level action and cannot be triggered from within the app itself. There is not really any other option if you are moving a contact in such a way that it will change context from one user to another (e.g. moving a household from one CHW Area to another).

A limited move functionality for moving a person contact from one place to another (as long as the user has access to both places) is possible to implement in the person edit form by allowing the user to update the parent value (as seen in your screenshot).

1 Like
3

thanks @jkuester
Once the contact has been cwitch to a new facility with cht-conf move-contacts action,

  1. are they given a new parent hierarchy ?
  2. in this example is the parent_id the new facility_id ?
  3. Are users supposed to clear the cache in the old facility
4

@cliff - another option is to run the CHT User Management Tool. This currently gives you a web GUI to prepare to move a contact and recently added a web worker running cht-conf will complete the move for you automatically.

1 Like
5

thanks @mrjones is this for 3.x to ?

6

CHT User Management Tool is for CHT Core 4.x only and does not support 3.x.

7

aaah i see , am using 3.x , going to upgrade

Thanks @mrjones

2 Likes
8

We love it when we inspire a deployment to upgrade to get a new feature!

That said, please be sure to prototype using the User Management Tool on a dev instance. It is a very new product that, as far as we know, has not been deployed outside of the 4 Medic hosted instances it’s currently used in.

While we’d absolutely love it if you used it and welcome an external use case, it will likely not be ready to go in something like a quick 5 minutes - a bit more work will be involved! Please keep us posted if you have any questions on this - a new user of a tool always has great eyes for seeing where our docs are lacking or where some code could be improved.

3 Likes
9

thanks @mrjones for this feedback , this is a tool we definitely will embrace once we upgrade

1 Like