Skip to main content

Sending Bed Assignments to Kipu (CRM)

Until now, a bed you assigned in Dazos stayed in Dazos. Kipu never heard about it, and the next time Dazos refreshed its picture of your beds from Kipu, your change could quietly disappear.

With this release Dazos can tell Kipu straight away: assign a bed, move a patient to a different bed, or free a bed, and that patient's bed in Kipu is updated to match.

The feature is off until you switch it on, and it only ever touches beds that came from Kipu in the first place.

Contents

1. Before You Start

2. Line Up Your Bed Names First

3. Turn On Bed Sync to Kipu

4. Using It Day to Day

5. What the Confirmation Message Tells You

6. What Does Not Get Sent

7. Frequently Asked Questions

1. Before You Start

You will need:

An administrator login that can open Settings.

A connected Kipu account.

Your bed names in Dazos matching the bed names in Kipu. Kipu identifies a bed by its name, so this is the one piece of preparation that matters. Section 2 covers it.

Access requirements: only an administrator can switch the sync on or off. Once it is on, it applies to everyone who books beds, with no extra permission needed.

If you cannot find the setting described below, your instance may not have this release yet. Contact Dazos support and quote CRM-3856.

2. Line Up Your Bed Names First

Kipu matches a bed by its name, so "Room 4 Bed A" in Dazos and "Room 4 - Bed A" in Kipu are two different beds as far as Kipu is concerned. Import your beds from Kipu before you switch the sync on, and the names will line up by construction.

Open the Bedboard screen. The import control sits in the toolbar:

1. Choose your EMR in Select EHR to import beds.

2. Click Import and confirm.

Tip: This control used to disappear after the first import. It now stays available, so you can re import whenever your beds change in Kipu. Re-importing matches beds by name and updates them rather than creating duplicates, and the confirmation dialog warns you before anything is replaced.

Important: Kipu needs a full occupancy structure before it will give you anything: a location, a building inside it, a room inside that, and beds in the room. If the import comes back with an error, check in Kipu that every location you expect has at least one building under it. A location with no building returns nothing to import.

3. Turn On Bed Sync to Kipu

Go to Settings, then EMR Settings, and choose Kipu. Open the Kipu — EMR Settings panel. You will find a Bedboard group below the data pull toggles:

Switch Send Bed Assignments to Kipu to ON and confirm. That is the whole setup. Here is where the group sits in the panel, under Core Configuration and Optional Data Pulls:

Tip: The setting is shared by every Kipu account on your instance, which is why it lives in the EMR level panel rather than under a single account. It starts OFF, including on instances upgrading from an older release, so nothing is sent to Kipu until you decide.

4. Using It Day to Day

Nothing changes about how you book a bed. Assign, move or free beds exactly as you do now, from the Bedboard screen or from the Admit dialog on an intake opportunity. Dazos passes the change to Kipu in the background.

What you do

What Dazos tells Kipu

Assign a patient to a bed

That patient is now in that bed

Move a patient to another bed

One single update naming the new bed, not a removal followed by an addition

Unassign a patient

That patient no longer has a bed

5. What the Confirmation Message Tells You

The message you already see when a booking succeeds now tells you what happened in Kipu as well, so you do not have to open Kipu to check.

Message

What it means

Bed updated in Kipu.

Kipu accepted the change. Nothing else to do.

Bed cleared in Kipu.

The patient's bed was removed in Kipu as well.

Not sent to Kipu yet: this patient is not linked to Kipu.

The patient does not exist in Kipu yet. The bed is saved in Dazos and travels with the patient the next time their record is sent.

Kipu did not accept the bed

update.

Kipu refused or could not be reached. Your booking in Dazos still stands. Support can retry it.

No mention of Kipu at all

Kipu is not involved: either the bed was created in Dazos rather than imported from Kipu, or the sync is switched off.

Important: your booking in Dazos always succeeds on its own terms. If Kipu refuses the update, the bed is still assigned in Dazos. The message tells you the two things came apart so you can follow it up, and nothing is silently lost.

6. What Does Not Get Sent

The sync is deliberately narrow, so it can never overwrite something in Kipu that Dazos does not own:

Beds you created in Dazos by hand are never sent. Only beds imported from Kipu are, because only those have a name Kipu recognises.

Patients not linked to Kipu are skipped. Dazos has no way to tell Kipu which chart to update, so it waits until the patient is linked.

A bed on a different Kipu account is skipped. If you run more than one Kipu account, a bed belonging to one account is never sent against a patient in another.

Nothing is sent while the setting is off, including on an instance where the setting has never been touched.

7. Frequently Asked Questions

Q: How do I turn this off again?

Switch Send Bed Assignments to Kipu back to OFF in the same place. Bed booking in Dazos carries on exactly as before, and Kipu simply stops being told.

Q: Will this change beds that are already assigned?

No. Switching the setting on does not push your existing bed list to Kipu. Only a bed you assign, move or free from that point on is sent.

Q: A booking says the patient is not linked to Kipu. Did I do something wrong? No. It means that patient has not been created in or matched to Kipu yet. Keep the booking; the bed is included automatically the next time the patient record is sent to Kipu.

Q: I renamed a bed in Kipu. What happens?

Re-import your beds so the names line up again. Until you do, Dazos is sending a name Kipu no longer recognises for that bed.

Q: Does this pull anything from Kipu?

No. This setting only sends bed changes out. What Dazos pulls in from Kipu is controlled by the Optional Data Pulls toggles above it, and those are unchanged.

Q: We use more than one Kipu account. Do I set this per account?

No, it is one setting for the whole Kipu connection. The safety rule that a bed and a patient must belong to the same Kipu account is applied automatically on every change.

Need Help?

1. Check the message on the booking confirmation. It names the reason whenever something was not sent.

2. Confirm your bed names still match Kipu, and re-import if they do not.

3. Confirm the Kipu connection is active in EMR Settings.

4. Contact Dazos support with the patient, the bed, the time of the booking and the message you saw, quoting CRM-3856.

Did this answer your question?