Can I add Specific Injections as Add On Tasks

In some clinics, there’s a desire to add specific injections (e.g., particular vaccines or medication injections) as add-on tasks to facilitate real-time collaboration.

For example, there’s sometimes a request to enable clinicians to choose from a specific list of injections (MenB, MenACYW, Pediacel, Pneu, Rot, MMR, Men-C, VZ, DTAP, MMR-V, HepB, Flu) via add-on tasks.

CHIME can be configured to support this — but we generally discourage it.

Why we discourage this …

CHIME is a clinic workflow collaboration and communication system, not an Electronic Medical Record (EMR).

Your EMR must remain the source of truth for anything related to patient medical care, including what was ordered and what was administered, and who did this.

Our concern is that enabling clinicians to indicate a specific injection via CHIME increases the risk that teams may:

• Treat CHIME as substitute record keeping

• Rely on CHIME data when the EMR is incomplete

• Expect CHIME to retain history in a way that supports auditing or clinical decision-making

Since CHIME is not designed for this purpose, we tend to discourage this internal workflow.

If you still want this configuration …

Occasionally, clinics advise us that they understand the above risks, but nevertheless, want this type of configuration. The most compelling reason we have heard is that the “alternative” is more risky and less reliable than CHIME (E.g. verbal instructions, sticky notes) and that using CHIME in this way would be an improvement in patient care.

To that end, if you’d like us to proceed, we ask that you acknowledge as follows in writing to us first:

“I (on behalf of myself and my clinic) acknowledge that CHIME has not been designed or intended to be an electronic medical record system, but instead is a clinic workflow collaboration and communication system. This feature and configuration has been added to CHIME at my request for my clinic's use because I consider it a more reliable and effective solution than the current status quo, but I acknowledge that such use is at my sole risk and that CHIME does not make any representations or warranties as to the suitability of its software for this purpose. I hereby waive, on behalf of myself and the corporate entities that I control, any and all liability of CHIME in respect of this feature and configuration. I hereby indemnify CHIME from and against any claims in respect of this feature and configuration.”

Once we receive this acknowledgement, we will be able to proceed with this type of configuration.