Apps‎ > ‎

Mosaiq Integration

Readonly Access!

Note that we are not proposing to use automated processing to update Mosaiq, only to read and process existing data.
At UNC we use Mosaiq QCLs to track the progress of patients through the simulation, planning, treatment, post-treatment and billing stages. We also use Mosaiq appointments to schedule a "consult" visit (where the diagnosis is entered), weekly "medical check" visit (to see if the patient is responded) and "follow up" visits (to track failures after treatment has ended).

This induces us to think that perhaps the information associated with QCLs and appointments could be "harvested" to track/show progress and prevent trivial errors:
  1. eWhiteboard status: a large monitor displays the planning status of each patient, color coded by how much time remains before the task's deadline. Broadcasting this info enables staff to choose their next task by taking the organizations queuing needs into account.  Step timing data (AKA analytics) can provide guidance to redesign hand-offs with a goal of increasing efficiency by:
    1. reducing critical processes (serial steps that block other steps),
    2. purposely designing overlapping processes for parallel work, and
    3. balancing steps across workers, teams, rooms/resources and schedules to maximize throughput.
    To reduce onscreen clutter, whiteboards can be customized, per display, to meet the needs of the staff in each physical location.

    Use cases: by optimizing clinical workflow, we reduce stress b/c staff are empowered, which may reduce errors, increase efficiency; research on workflow; Kaizen input

  2. Schedule reporting: Crystal Reports gathers and analyzes patient statistics to produce Excel spreadsheets or nicely formatted printed reports, but it's tedious to run. If we could run reports on a regular basis (eg, daily), then multiple reports could be emailed to a supervisor who would then spend time reviewing them in bulk, rather than time generating the reports.  Sending spreadsheets to a disk on schedule (eg, every weekday @ 8am and 4pm) is also an effective way to gather data for time studies, automatically generating up-to-date graphs/charts to be viewed on a (private) web site.

    Use cases: by predicting future budgets; research (trolling for patients, hooking research into patient flow)

  3. Check business logic: the clinic follows many rules when scheduling tasks, AKA business logic, that are optimized to satisfy requirements of insurance companies, doctors, workflow, physical/practical needs, etc.  Automated spot checks can be devised to notify people about potential trouble spots, such as:
    1. verifying that a pacemaker was properly accounted for in a plan (display in PLUNC)
    2. that a sim review was scheduled after a charge was captured (email supervisor if not)
    3. that a billing expert has properly converted a treatment to a charge
    4. that the number of fractions delivered is close to the number planned
    5. that the delivered fractionation schedule deduced from a treatment calendar exceeds accepted biological limits, etc.

    Use cases:
     saves time (catch clinical issues sooner); provides a layer of comfort; causes us to define our business logic
Comments