2022-07-26 Release 125

Modified on Wed, Nov 8, 2023 at 5:30 PM

Features

Patient Merge Sanity Check on MRN

Update as of 2022-07-28

  • We have released (in R125) a small change to the patient merging logic that will let two patients merge as long as the merge does not add any new MRNs to the patient's record.
  • The way the patient MRN sanity check will now work is the following:
    • Let's say the hospital has the patient_mrn_identifier_limit setting set to 1
    • If two patients are about to be merged, and the merge will result in that patient's ControlCheck record having more than 1 MRN, then the merge will not happen
    • If two patients are about to be merged, and the number of MRNs for the patient already exceeds the patient_mrn_identifier_limit, and the number of MRNs after the merge will be the same as before the merge, then the merge will be allowed, even if that patient record already has more than 1 MRN.

Ability to Automatically Map New NDCs from Wholesaler Data

Hospitals buy new NDCs all the time, and we had an opportunity to automate a painful piece of the ControlCheck workflow: med mapping. Customers who are set up on the automated Wholesaler Invoice feed will realize the added value of saved time to review drug discrepancies in the Pharmacy Module with this new update. When a new NDC is purchased and the invoice sent to ControlCheck, our Formulary Service will ping Medispan to automatically map that NDC to the right ControlCheck med for audit reconciliation. Maybe the previous NDC they purchased is no longer available or is currently on shortage; in this case, they still need the drug, so they will purchase what is available from a Wholesaler they work with. If the NDC returns valid results from Medispan, it will be automatically mapped and no manual work is required for the customer. If that NDC is also a supported form factor for auditing and has a valid DEA code of 2-5, indicating the control schedule of the NDC, then we will set that NDC to be automatically Audited in ControlCheck.

Let's use NDC 60687-638-01 as an example (11-digit NDC: 60687063801). This NDC is a LORazepam 1 mg Oral tablet. The hospital purchased this NDC for the first time on Dec 17, 2021 and they were invoiced for 300 tablets. When ControlCheck receives the Invoice payload from our EDI service, we'll spin off a workflow that will automatically map that new NDC to a ControlCheck medication, as seen in the image below. This NDC returns a Schedule IV (4) DEA code and is a form factor we support so we will automatically set this NDC to be audited at this site and will display the Invoice information to the Pharmacy Auditor for review. If there is a corresponding load of the 300 tablets of LORazepam, then ControlCheck will group those events together and auto-resolve the case.

Upgrades & Fixes

  • Updated the text on Pharmacy Audit table to be more consistent. If the event summary does not contain any Invoice events, then we will display the text "No invoice events found". If the event summary does not contain any Load events, then we will display the text "No load events found".
  • Updated the Patient ID/Name search on the Audit 2.0 page to be more performant.
  • Updated the Admin Tools Create Generic page to return all supported form factors so that Admins can easily create new generics for new dosage forms if the same concentration already exists for another dosage form. For example, let's say the generic fentaNYL 50mcg/mL already exists for the injectable form factor; with this update, an Admin can now add a new generic of the same concentration, but for another form factor, such as IV.
  • Updated our QA environment to have a hospital that refreshes data each night (like in Demo) so that there is always a hospital with recent test data for our QA engineers to test with.
  • Set up EDI in the ControlCheck Staging environment for proper regression testing of the new EDI workflow.
  • Fixed an issue with duplicate-appearing medications in a hospital's ControlCheck formulary. The issue would manifest through a variety of different workflow (e.g. formulary upload, split-a-med workflow, etc.) so we have added validation to the system that will prevent two meds from having the same generic drug, wholesaler multiplier, threshold percentage, and Audit State.
  • Fixed an issue that was allowing a User to be mapped without a first or last name.
  • Fixed a highly frustrating issue with the Save My Place feature that auto-scrolls the Audit page after editing an event summary. The page would auto-scroll as if it had a mind of its own. This issue should be fully addressed. If you experience this issue again, please reach out to Support immediately.
  • Fixed an issue with the Assignment feature that was unexpectedly removing all assignees from an event summary if at least one user was being purposely removed as an assignee.
  • Fixed miscellaneous issues with the Formulary File service.

Upcoming Features & Bug Fixes

The feature enhancements and bug fixes below are tentatively scheduled the go live on the dates listed. For a full rundown of all new features and fixes, make sure to read the Release Notes articles for those dates.

Release 126 - Week of 08-09-22

  • Upgrades to the automated Wholesaler Invoice data feed to solve a use case that includes a hospital purchasing an NDC from a new Account Number they have not used before. This update ensures that an unmapped Location is created for the new Wholesaler Account Number so that a Manager or Admin user can map it into the correct department.
  • Upgrades to the Shift Analysis v2 Report that incorporates Kronos (HR) Time and Attendance data.
  • Further performance enhancements to the Patient ID/Name Search on the Audit page.
  • Ability to 'select all' Departments with the click of one checkbox when creating new user Security Roles.
  • Ability to run a report for a certain provider directly from the Audit event summary cards.

Release 127 - Week of 08-23-22

Rollover Release Items
Any of the items mentioned above that are delivered in R126 will be delivered in R127. 
  • Updates to the "unspecified" department in ControlCheck for an enhanced experience of Location/Department management in ControlCheck.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article