3. Product: Inpatient clinical¶
Patient care is multi-disciplinary. The circle of care for a patient may involve doctors, nurses, clinical support staff e.g admissions clerks, case managers, payors, guarantors, pharmacists and others. This multidisciplinary role setup is made harder by the need to balance between access and confidentiality - what does each party need to know in order to do their job? This is made even tougher by the need for mobility.
Note
Information Security
This guide assumes that there shall be fine grained role based access control. The permissions used shall be granular, so that is shall be possible to grant or deny access to any screen or section of a screen. It shall also be possible to grant view only rights.
- Access shall be restricted on the basis of:
- user groups
- user types
- individual patient charts
- locations e.g nursing floors, clinics
- patient type e.g VIP, confidential patients
- a combination of all of the above
Logged in sessions shall be timed out after 10 minutes. The user shall be locked out from further login attempts after three incorrect login attempts. Each lockout shall be an hour long.
All entries shall be time stamped and audit trailed.
The system will need to support secure logon - with hardware tokens.
Note
Online Help
The system should embed online ‘help’ and first-use tutorials.
For clinical services, the need to design for high distraction environments and for task efficiency is paramount. Many of the existing products have failed to gain adoption in clinical settings in part because they are perceived to be more cumbersome than paper.
3.1. Theme: Scheduling¶
The scheduler will be available to administrative staff ( e.g registration clerks ), clinical staff ( e.g doctors and nurses ) and even to patients themselves.
This feature should work for both single clinics and large multi-site healthcare businesses. For a multi-site operation, the calendar should be synchronized enterprise-wide.
A medium- to large- provider will typically have many concurrently scheduled routine clinics e.g paediatric, antenatal, postnatal, family health, diabetes, chest, well baby, child welfare, immunization, lamaze etc. There will also be a sizable number of specialist clinics e.g neurosurgical, obstetric, cardiology, neurology etc
3.1.1. Epic: Operating room ( theater ) scheduling¶
This, too, can operate in a centralized or decentralized manner.
Some departments that are not classically thought of as ‘surgical’ e.g cardiac catheterization, interventional radiology and endoscopy will use scheduling facilities that are similar to what is described for operating rooms.
Preference cards for surgical and anaesthetic staff define the supplies needed for each case.
Note
- As a:
- user with OR scheduling duties e.g surgeon, theatre nurse, ward doctor
- I need to:
view daily and weekly schedules by operating room, department, surgeon, anaesthesiologist, patient etc
capture the following scheduling data: patient name, age, gender, ward and bed number, medical record number, contact details, diagnosis / indication, planned operation / procedure, surgeon, booking date and time, name of scheduler, estimated time of surgery, anaesthetist / anaesthesiologist, type of anaesthesia, assisting surgeon(s), scrub nurse, special requirements, known allergies, comorbidities, physician, special requirements e.g implants
scheduling of recovery locations
shift start times automatically when surgeries are added
swap cases - individual or entire rooms - without reentry of data
automatically shift start times when cases are cancelled
speed scheduling - next five available conflict free time slots
scheduling of multiple procedures for the same patient cases
scheduling of multiple procedure and multiple surgeons for one case
re-sequence the cases in the final list, as necessary
surgeon’s verification of the operating list before it starts
color coded status of the operating list - provisional, verified, final
printing of operating lists
transfer patients from one surgeon to another
online waiting list and reservations, with priorities
standard turnover and setup times per case - added to case duration
manually override standard turnover or setup time per case
automatically use surgeon’s average case time when scheduling a case
OR status whiteboard
book slots - with the following conveniences:
- drag and drop rescheduling e.g swapping cases between rooms
- automatically locating the next available time slot
- wait lists
- ability to select durations based on the case, surgeon etc
- moving cases between surgeons and operating rooms e.g due to schedule changes
- cancelling or holding cases, with reasons indicated
- free text notes for bookings - comments for OR staff
- automatic checks for resource conflicts
- override conflict checks and availability block conflicts - with a reason given
- associate bookings with orders
A booking may involve multiple surgeons and multiple rooms ( e.g OR and recovery )
- edit bookings
- manage equipment availability / unavailability
- schedule equipment for use in surgeries
- manage operating rooms e.g set rooms aside for specific procedures
- define availability blocks for surgeons, rooms, anaesthesiologists, support staff ( scrub nurses etc )
- define surgeon preferences - allergies ( e.g allergies to latex ), hand size, handedness ( left or right )
- reschedule e.g because an emergency operation took precedence over the scheduled operations ( common occurrence )
- reschedule cases that have not started within a defined threshold e.g 30 min
- reactivate a cancelled case, with retrieval of all previous data
- surgical packages - with the ability to charge for extra items and theatre time
3.2. Theme: The patient record¶
An individual patient’s record shall be accessed via a dashboard that ‘brings together’ all of a single patient’s clinical records.
Clinical and billing information should be displayed in reverse chronological order by default; more recent events are of greater interest than remote ones.
All patient records shall be accessed via the same interface, whether current or historical. “Archiving” is a back-end level concern that should be auto-managed.
The coded sections of each patient record shall use the following terminologies:
- ICD-10 ( provisional and final diagnoses )
- ICD-O ( oncology )
- LOINC ( investigation orders and results )
- SNOMED ( the detail of the clinical record itself )
In addition to having SMART apps for custom templates, custom visualizations etc, the system should support an arbitrary number of custom print templates.
3.2.1. Epic: Care plans¶
Plans of care range from medication or procedure plans to lifestyle interventions. Many of these plans of care will be multi-disciplinary e.g involving physiotherapists, occupational therapists and speech therapists.
Nursing care plans might include risk factors, signs and symptoms, outcome criteria, nursing interventions and discharge criteria.
Note
- As a:
- clinical user
- I need to:
- define individualized plans of care - that might be multi-disciplinary. The system should assist this process by providing critical pathway guidance and decision support
- document care goals and outcomes
- define acuity levels and early warning signs - track, filter by patient / nursing unit, date, shift, care level
- edit or discontinue all or part of any plan of care
- note target dates for interventions on care plans
- access previous plans
- record interventions ( date, practitioner, intervention notes )
- assessment at variu=ous stages depending on condition and level of nursing care e.g on admission, on change of condition, post-op, every 24 hours, on discharge etc
- reminders, checklists and planning documents
- standard care plans - linked to diagnosis
- define nursing checklists e.g change of shift, nursing round, pre-op
- alerts for planned care when the time elapses
- fluid chart automated cumulative balances
- free text entry of non-standard care plans
- nursing progress notes and observations; progress notes may be SOAPIER - Subjective, Objective, Analysis, Plan, Intervention, Evaluation and Review
- entry of all medical equipment that has been connected to the patient
- define and support patient call system
- define high priority patients
- chaplaincy service requests, alerts, request list, notes, follow up ( pre-supposes capture of patient religion )
- shift handover summary
- print care summaries for patients
- print active care plans by patient
3.2.2. Epic: Operating room documentation¶
Operating room documentation is multidisciplinary. There are surgeons, surgeons’ assistants, anaesthesiologists, various nursing roles...
Note
- As a:
- operating room nurse or doctor
- I need to:
- access the complete patient record
- work through pre-operative checklists - consent, investigations, blood requests, pre-anasethesia checks etc
- enter pre-, intra- and post- operative documentation using templates. This includes text, outcomes, anaesthetic medications, implants, explants, items used, medication administration record, transfusion administration record, pre-operative diagnosis, post-operative diagnosis, indications, specimens, complications, findings, notes etc
- anaesthetic documentation includes: anaesthesiologist, start and stop times, anaesthesia types and agents, complication codes, free text
- add addenda to documentation that has already been finalized
- register specimens and dispatch them to the relevant labs
- track usage of consumables and services and submit charges to billing as they are added; this also updates floor inventories. Bar code scanning or similar methods could be used.
- track implants and explants - for purposes of tracking in the event of a recall
3.2.3. Epic: Peri-operative care¶
Note
- As a:
- operating room nurse or doctor
- anaesthesiologist or anaesthetist
- I need to:
access the complete patient record
generate and print patient collection cards
record the exit of the patient from the ward / department and notify theater
verify the pre-op checklist
admit, acknowledge and document patient arrival in the holding bay, OR, recovery bay and checkout ( with bar code scanning )
support verification of patient identity and procedure to be performed
validate the identity of the patient by scanning the bar code
record the start time of reach avigity - patient arrival, administration of anaesthesia, start of surgery etc
color coded tracking display: checked in, awaiting procedure, procedure in progress, procedure completed, in recovery, checked out
cancellation, with reasons
WHO surgical checklist
- peri-operative data:
- pre-op and post-op diagnosis
- time in and time out
- delay time and reason
- allergies
- meds and/or IV, dose, time
- prep performed
- pre-op and post-op free text notes
- type of anaesthesia and anaesthesia agents
- X-ray takens
- implant log data e.g serial number, lot number, size
- specimen data
- blood loss
- assistant surgeon(s) name
- circulator nurse(s) name
- scrub nurse(s) name
- start and stop times for anaesthesia
- start and stop times for surgery
- complications
specimen dispatch list
consistent and organ disposal
requirements per procedure ( basket ) - to request from theater store
interface with CSSD for sets
return of unused supplies
documentation in death registry
3.3. Theme: CPOE¶
Computerized ordering covers the domains of pharmacy, lab ( pathology, microbiology, hematology etc ), radiology / imaging, diet, nursing care, procedures ( e.g specialized assessments ), physiotherapy, occupational herapy, catering, transport, theater etc
Orders share the following characteristics:
- time and user stamped
- ‘signed’ by the ordering clinician or on behalf of the ordering clinician
Some orders ( e.g those entered by medical students ) may need verification before they are fulfilled.
Results share the following characteristics:
- time and user stamped
- ‘signed’ by the issuer
- patient name
- hospital number
- date and time of order
- date and time results were last updated
- alerts for changes / amendments
- test name
- visual cues for abnormal results
It should be possible to define custom result templates.
3.3.1. Epic: Patient diet orders¶
Diet orders could be entered by nursing staff, kitchen staff or clinical staff.
Note
- As a:
- nurse, kitchen staff member or clinical staff member
- I need to:
- prescribe diet for inpatients, outpatients, visitors, hospital staff etc
- record patient specific diet preferences, which should be displayed to anyone involved in making or modifying diet orders
- easily prescribe special diets e.g cardiac diet, normal diet, diabetic diet, renal diet
- prescribe therapeutic diets e.g total parenteral nutrition, tube feeding or supplemental feeding
- view meal requests, by day and mealtime
- cancel meal requests manually; the completion of a discharge process or the recording of a patient demise should trigger auto-cancellation
- view ingredients and calorie values for any available meal
3.3.2. Epic: Blood orders¶
Orders for blood can come from any of the clinical areas.
Note
- As a:
- doctor or nurse
- I need to:
- make requests for blood or blood products for my patients. Each request indicates: reason, urgency, patient’s blood and rhesus types, patient location, date needed, location needed etc
- receive notifications on availability / non-availability and issuance of requested blood / blood products
- perform electronic specimen cross-matching
3.4. Theme: Admissions, discharges and transfers¶
This set of features covers both ‘conventional’ (e.g surgical, medical, paediatric and specialized wards ) and short stay ( e.g day surgery, some endoscopy and some in-vitro fertilization ) admissions.
Every ward will be set up with: name, status, number of beds, specialty and gender. Rooms will have varied occupancy - single, double, ward bed, deluxe, suite etc. They will also have different charges. Beds will have different status codes e.g occupied, available, reserved, empty etc.
3.4.1. Epic: Real time bed board¶
The bed board is a real-time graphical representation of bed availability / status across the healthcare enterprise. It is the digital world equivalent of the traditional whiteboard that is often found near the nursing desk in hospitals - only better, by being realtime and hospital / enterprise wide.
The bed board shall be visible from every point of care that participates in the admission, discharge and transfer processes.
Note
- As a:
- user with an admissions role ( e.g admissions clerk, nurse )
- I need to:
- have access to a realtime bed board that shows patient names, patient numbers, visit (IP) numbers, age, status, type, gender, bed typem insurance information, clincial needs ( e.g oxygen or isolation ), expected length of stay / discharge date, leave of absence status, confidentiality status, admitting diagnosis and location
- be able to filter the bed board by department, ward, room, patient type etc
- be able to generate a printable patient census on demand, filterably by ward, nursing station, practitioner, expected discharge date etc
- be able to view the bed status of other facilities in the enterprise
- be able to distinguish occupied from unoccupied beds
- be able to distinguish admitted patients from others in patient listings e.g by a bed icon
- be able to quickly see unoccupied beds, and the corresponding wards / rooms
- be able to block out periods of time when beds are unavailable; these periods will have lower and upper date / time bounds
- be able to predict bed shortages
- be able to track a single patient’s movements during their stay
- be able to quickly access pending transfers, discharges, emergency registrations, demises etc
- be able to set up custom floor plans and designate certain beds as being for certain patients e.g gender specific rooms / beds, beds for infectious disease patients etc
- be able to set aside beds / rooms for observation patients; these rooms could potentially be billed by the hour
- be able to generate an interim bill for any patient that is currently admitted, right from the bed board
- produce and in-patient therapeutic procedures list
- Because:
- I need to be able to give my patients quick and accurate answers as I guide them through the admission process
- I need to have accurate patient censuses at shift handover times
- I need to quickly access information on bed status at other in-network hospitals when I am planning a referral or admission there
- I need to be forewarned on impending bed shortages so that alternative arrangements can be made
- I need to eliminate time wastages from placing patients in beds that are not usable e.g in a room that is undergoing maintenance
- I need to be able to adapt to developments in my hospital e.g a new ward / wing, an outbreak that causes an improptu isolation ward to be set up etc
3.4.2. Epic: Outpatient ‘discharge’¶
This is the case for most patients - all who needed simple outpatient care or even mere reassurance.
‘Discharge’ from the emergency room could involve:
- sending the patient home / back into the community ( the traditional meaning of discharge )
- sending the patient to a ward ( admission to hospital for further care )
- sending the patent to another facility for further care ( usually called referral )
The details of these three ‘modes’ of discharge are covered in the sections of this document that deal with ADT ( Admision - Discharge - Transfer ).
Note
- As a:
- emergency room clinical worker ( doctor, nurse )
- I need to:
- be able to discharge a patient who only needed outpatient care once their care plan has been implemented
- print discharge instructions that the patient can take home with them. These discharge instructions can be customized for each patient, by picking relevant instructions from the patient’s record. The system should provide for multiple customizable discharge templates.
- generate a discharge prescription and send it to the Pharmacy
- schedule a follow up appointment
- generate a return to work or school letter for the patient on request
- generate a patient survey and send it to the patient portal
- Because:
- most patients who come to the emergency room will be discharged home in a matter of hours
- patients who get clear instructions on discharge do better / follow their treatment plan better
- most patients will be discharged with an prescription for home drugs
- some patients may need to come back, esp. if we have decided on ‘empiric therapy’ ( treat on a presumed diagnosis, not a definitive / confirmed diagnosis )
- some patients will need to get a doctors’ letter for their workplace and school
This feature interacts heavily with billing - the discharge cannot be completed unless the patients bill is settled or all the details needed to claim it from a corporate payer ( insurer / employer ) are captured.
3.4.3. Epic: Admissions¶
The pre-admission process is focused on information capture.
Admissions can be triggered from several points of care e.g A&E, theater, clinics etc. It follows then that these features will be exposed to multiple user roles.
There should be continuity between the emergency room and the inpatient departments i.e the same patient record should be used after the patient is admitted.
Note
- As a:
- user with admission responsibilities e.g an admissions clerk or a nurse
- emergency room clinical worker ( doctor, nurse )
- I need to:
- view a queue of patients awaiting admission / admission requests
- be able to request an admission for the patient
- view ward / room / bed availability
- request pre-authorization for insured patients that need admission
- have instant access to the billing status of each patient in my queue
- be able to send patients to the billing clerk’s queue for the payment of their deposits
- be stopped by the system from re-admitting a patient whose previous bill is not settled
- be stopped by the system from allocating a bed for a cash patient whose deposit is not paid
- capture all vital information for patients who are due to be admitted. This information includes room preferences e.g ‘Prefers Standard Room’ / ‘Prefers Private Room’. It might also involve updating the existing patient record
- admission data includes: date and time, medical record number, admitting physician, attending physician, admitting diagnosis, last inpatient date, text, primary and secondary insurance, VIP status,
- verify eligibility for insured patients and obtain a pre-authorization where one is needed
- reserve a room for a patient that is going through the pre-admission process; this could be a room or bed that is currently occupied but can be reasonably expected to be available at the time the admission completes
- pre-admission reservation number
- assign an inpatient number at the start of the pre-admission process
- enter clinical notes
- enter orders e.g lab and medication orders
- access a listing of pre-admitted patients that can be filtered by date and time, location etc
- cancel a pre-admission process
- reschedule / change the target admission time for a pre-admitted patient
- admit newborns
- Because:
- capturing all the information up-front will lead to a smoother admissions process
- insurance authorizations usually take time; it is best if they are done early
- rooms can be scarce or ephemeral in a busy hospital; I need to reserve it in order to be reasonably sure that my patient will get a room
- the inpatient number is used to tie together the patient’s inpatient records, including any orders that may be made in the pre-admission period
- the patient could already be under active management e.g in the emergency department, hence the need for ongoing clinical notes
- it is essential to have visibility into the pre-admission queue / workload, for optimization and planning
- pre-admissions can be aborted e.g in the event of a patient’s demise
- pre-admissions can be delayed, e.g in the case of an elective surgical procedure that is moved to another date after a surgeon’s or anaesthetists’ review
- for most patients, the admission process starts at the casualty / emergency department
- I need to be able to deal with the two most common hold ups in the process: ward / room / bed availaibility and billing problems
- I need to quickly advice my patient - or my caregiver - on whether they need to go through billing first OR on the status of their insurance pre-authorizations
- I need the system to help me avoid errors that could cause revenue leakage
3.4.4. Epic: Assigning a bed to a patient¶
The ward / bed / room assignment has billing implications; for example, private suites are more expensive than shared standard rooms, per day. Some patients may have high end insurance that entitles them to expensive rooms; others might only be able to afford cheaper ones.
This is the last step in the ‘admission’ process - it is the point at which the whole admission ‘crystallizes’.
Note
- As a:
- user with admissions responsibilities ( admissions clerk or nurse )
- I need to:
- assign a bed to a patient, based on their preferences and ability to pay ( deposit paid, insurance category )
- be able to charge a lower rate to a patient who is placed in an expensive room / bed because of lack of availability of cheaper rooms / beds
- be able to assign confidential / VIP status to certain patients; their records get sealed for access by only a select ( named ) list of caregivers
- print patient labels
- enter the expected length of stay - which can be used to give alerts when the patient is near the end of that lenght of stay
- assign a patient to an overflow bed if their assigned room / bed is occupied
- alert porters and ward staff when a patient needs to be transported to the ward
- admit a newly born baby to the mother’s bed; the baby should be able to get their own record and inpatient number later
- rely on the system to check for conflicts for me e.g prevent me from assigning a female patient to a male bed
- be able to overrride system conflict warnings ( with a reason kept on record )
- be able to transfer patients between wards and beds, noting the reason for transfer each time. The transfers may or may not trigger new rates.
- be able to swap patients between two beds
- assign beds to observation patients - who are not actually in-patients
- transitioning patients from observation to inpatient and v. versa
- Because:
- it is my job to meet patients’ needs as well as I can
- I need to solve emergent problems e.g temporary capacity problems that can be worked around by admitting some patients into more expensive rooms without prejudice to the patient
- I need to communicate efficiently with ward staff and porters
- I need to be able to correct errors or undo temporary choices that were made due to capacity challenges
- I need to be able to make judgement calls e.g in times of emergencies such as outbreaks, when a female room could be used for male patients or vice versa
3.4.5. Epic: Discharge from inpatient or day case admission¶
This feature’s scope runs from discharge planning to post=discharge actions e.g housekeeping.
The discharge process is one of the processes that is most commonly ‘broken’ in today’s healthcare settings. The norm is for it to be a disorganized mess, with the patients / caregivers tossed between offices and taking hours for what should be a routine process.
Note
- As a:
- user with discharge responsibilities ( e.g discharge clerk or nurse )
- I need to:
- receive relevant ( to my location or job station ) discharge planning alerts based on expected discharge dates
- receive confirmed discharge alerts after the doctors make the discharge decision; these include information on the discharge e.g doctor , reason ( normal, against medical advice, absconded, demise ), dischage diagnosis, date and time of discharge, clinical discharge notes / summary
- be able to view pending discharges by nursing station
- be able to work through a discharge checklist - nursing actions, patient / billing actions, discharge medications and equipment, post-discharge care instructions e.g wound dressings
- customize discharge checklists / discharge plans - by patient, diagnosis, surgery, physician
- be able to process unused drug returns from the patient
- be able to cancel undone investigations and have them removed from the patient bill
- automatically discontinue inpatient medications upon discharge
- be able to schedule follow up appointments
- be able to cancel the discharge and notify relevant departments ( e,g Pharmacy, kitchen, lab, ward nursing desks ) of the cancelled discharge
- be able to notify housekeeping after the discharge - to prepare the bed for another patient
- be able to notify other relevant departments e.g cancel kitchen orders
- be able to re-admit patients whose discharge is rescinded before they leave the ward
- be able to initiate a ‘leave of absence’ - essentially a ‘soft discharge’ where the patient is sent elsewhere ( e.g ICU ) but is expected back
- be able to view a summary of the discharge queue / pending workload, by station
- print patient discharge instructions - educational and functional e.g drug monographs
- send patient post-discharge surveys to the patient portal
- handle death notifications
- handle discharge against medical advise
- Because:
- the process will be more efficient if all involved parties have advance information
- if I can see the points at which a discharge process has stalled, I can make targeted interventions
- the post-discharge care process is as important as the intra-hospital care process; I need to set my patients up for success by equiping them with the right information and scheduling follow-on appointments
- housekeeping need to turn the bed around quickly so that another patient can be admitted into the same bed
- a discharge may be cancelled because of emergent clinical or administrative problems
- other departments e.g the kitchen may need to adjust their workplans as a result of the discharge
3.4.6. Epic: Refer the patient to another facility¶
These referrals occur for these common reasons:
- the patient is unable to pay e.g referral from an expensive private hospital to a public facility
- the level of care needed is unavailable e.g referral from a smaller hospital to a teaching and referral hospital
Note
- As a:
- emergency room clinical worker ( doctor, nurse )
- ward nurse or ADT officer
- I need to:
- be able to discharge and transfer a patient to another facility
- generate discharge / transfer notes - containing clinical information picked from the patient’s record
- view billing status, so that I can advice the patient or their care givers accordingly - e.g. to clear their bill
- Because:
- we commonly transfer patients who need more specialized care
- we commonly transfer patients who are unable to pay, after delivering the legally mandated emergency care
The referral information could be printed ( common case in our context ) or sent via a health information exchange ( what we are building towards ).
3.4.7. Epic: Automatic charges¶
In a hospital, there are a lot of automatically added charge items e.g charging for inpatient beds each day, automatically charging for every test that is ordered etc
Even though these charges are automatic, there still needs to be some level of human oversight.
Note
- As a:
- billing user
- I need to:
- see room and bed charges that have been calculated automatically every day
- see charges that have been added as a result of provider orders or nursing activities
- see charges that have been added as a result of a workflow step e.g a standard admissions charge
- see automatically calculated rebates e.g NHIF bed rebate
- with authority ( maker - checker ), remove or reverse charges
- Because:
- adding these routine charges or rebates manually would quickly overwhelm the billing team
3.5. Theme: Blood Bank¶
The blood bank supports inpatient, surgical and emergency departments.
3.5.1. Epic: Blood bank dashboard¶
Note
- As a:
- blood bank employee with coordination duties
- I need to:
- access listings of blood requests for clinicians
- enter manual requests ( request that come as paper instead of ‘online’ )
- be notified when a new request is received via CPOE
- prioritize requests for blood e.g higher priority for surgical emergencies
- conduct cross-matching for incoming patient requests
- issue blood and blood products to fill requests
- accept returns of unused blood that is in restockable condition
- perform transfusion reaction workups
- see a patient’s blood bank history when ordering
- Because:
- responding quickly to blood requests can save lives
3.5.2. Epic: Donor register¶
Note
- As a:
- blood bank employee with donor registration duties
- I need to:
- maintain a donor register - which will have, among other details, contact details, donor types ( patient / relative / autologous / platelets etc ), donor vitals, donor lab readings e.g Haemoglobin, donor notes, donation history etc. The donor register will allow for search by blood group, gender, date of birth etc. For each donor, track name, sex, date of birth, marital status, contacts, occupation, blood group, blood type, antibody profile, donation dates, comments
- link to donor medical history
- display donors full history of donations, tests, results
- consent for donors
- mark permanently deferred donors e.g due to sero status
- mark temporary deferral e.g weight, age, menses, time lapse period
- warn the user during registration if the user is on a deferral list
- generate an alert when a donor attempts to donate while deferred
- trace all recipients of a particular donor
- trace all donors of a particular recipient
- recall donors who are due for next donation via automatic notification
- list of regular donors for rare blood groups
- track minimum / maximum donation levels and generate alerts when necessary
- support donor inquiries
- generate birthday / anniversary new year/ Christmas wishes for donors and reminders for next donation
- Because:
- the blood bank needs to have accurate information for emergency blood outreach
- donor tracking information will help the department plan blood drives
3.5.3. Epic: Handling blood donations¶
Note
- As a:
- blood bank employee with blood donation duties
- I need to:
- receive donations - with the ability to maintain bleeding data, blood bag data, blood bag expiry, amounts drawn, time in and out
- tag blood bags with RFID tags and bar codes; the bar codes should be ISBT 128
- conduct standard tests on donated blood, as per national guidelines e.g BP, HB, weight, temp, pulse
- conduct rhesus typing and antibody screening on donated blood
- process donated blood - in whole or separated form - into bar coded blood bags
- dispose of unacceptable blood
- carry out repacking
- carry out aliquoting / pooling
- scanning and printing of ISBT128 labels
- maintain an audit trail of all processes from the vein of the donor to the recipient
- manage autologous and directed donations
- link directed and autologous donations to the intended recipient even if the intended recipient is not yet registered
- screening and compatibility tests
- phlebotomy - facilitate sample collectionn and processing
- entry of phlebotomy information, including start and end
- track specimens through transport, receipt, testing, storage, testing, final disposition
- generate bar coded labels and collection lists
- log specimens into storage and quickly locate them by rack, position and refrigerator when additional testing is required
- provide a list of specimens to be discarded according to a lab defined retention period
- entry of blood bag types and lot numbers
- antibody, antigen and serology specimens
- capture and provide reagent log details e.g lot number, batch number, expiry date and manufacturer
- quarantine non-conforming blood and blood components
- quarantine products from prior doations wtih HIV , HEP C HBV, syphilis
- all tests on a donated unit must be completed before transfer to stock inventory
- generate and print black and white ABO/Rh labels on demand
- notify donors of test results
- authorized override of cross-match restrictions in emergencies
- Because:
- blood donations are the primary way in which the blood bank receives ‘new stock’
3.5.4. Epic: Management of blood and blood product inventory¶
Note
- As a:
- blood bank employee with supervisory duties
- I need to:
- access inventory information for blood and blood products
- track each blood product from donation through receipt into inventory, testing, modification, transfers to other facilities and final disposition
- be alerted on reorder levels
- be alerted on critical / panic levels
- be able to reserve blood / blood products for anticipated uses
- access donation and screening reports
- be able to receive blood and blood products from other centers
- Because:
- avoiding stockouts helps avoid unnecessarily suffering or death
3.5.5. Epic: Blood Component Preparation¶
Examples of blood components are fresh frozen plasma, packed red cells, platelets, cryoprecipitate etc
Note
- As a:
- blood bank user
- I need to:
- support blood component preparation: capture the date of preparation, date of expiry, storage of each component, link to donor profile
- track deviations and unexpected events during manufacture of a finished product
- generate a list of donor units waiting to be label verified
- maintain a reference table of blood components and batch products with label bar codes
- print color coded ABO labels ( O - Blue, A - Yellow, B - Pink, AB - White )
- automatically update the donor / patient records once test results are reviewed and verified
3.5.6. Blood storage and distribution¶
Note
- As a:
- blood bank user
- I need to:
capture the following information for each individual unit: donation number, ABO and RhD group, component code, expiry date, expiry time
allow entry of the component information above by scanning of the bar codes
allow the following component characteristics to be retained against each component: antigen typing, CMV antibody status, gamma / X-ray irradiation, Hb S status, high titre flags, volume, comments
allow the system to generate an alert if freezing time requirements are not met for cryoprecipitate
ability of the system to generate an alert if a unit of blood is not leukoreduced within the appropriate time frame
ability of the system to provide component inventor control, processing and tracking
manage and automatically update inventory based on donated units and units issued
prompt for the following before issuance of units: identity of the individual collecting the units, patient’s MRN, destination of the unit, barcodes of the units
mark specific units that should not be used
modify expiration date and time for products
allow expiration date to be overridden with proper clearance
track expiry dates and manage issuance of units based on this
track expiry dates of units in stock and generate an alert when about to expire
generate a list of units in order of remaining shelf time for any unit type and ABO group
record unit movements, including transfer between reserved and unreserved stock, transfer to and from satellite refrigerators, issus to users, transfers to other departments
return of unused products
recall of units, with reasons
log the amount of time a unit was out of the blood bank for returns and recalls; alert if above policy threshold
recall, with reasons
prevent dispense of incompatible blood and components
match needs to units e.g patients who need irradiated or antigen negative blood
allow emergency issue
automatic cancellation for discharged patients
display patient specific blood bank info: units held for the patient, current specimen status, ABO/Rh, antibodies and antigens, transfusion needs, current testing status / results, current order status, transfusion reactions
- reports:
- daily transfusion log
- units received by donor
- units issued per patient based on component type and blood group
- cross match requests - by location, diagnosis, doctor etc
- transfusion reactions
- disposition
- donor units ready to be label-verified
- stock
- request and demand
- expired blood products
- reserved, recalled, returned units
3.6. Theme: Support services¶
3.6.1. Epic: Kitchen management¶
The kitchen contributes directly to patient care, especially for inpatients. It is also a significant cost and revenue center - making it relevant to overall profitability.
Large hospital kitchens may want to conform to ISO 22005.
Note
- As a:
- kitchen supervisor
- I need to:
- define different menus: regular, renal, low cholesterol, diabetic, light and gastric, children’s ( above 9 months ), children’s ( below 9 months ), toddler;s menu, a la carte, special diet request, kitchen feed, banqueting
- access listings of patient meal requests for each meal - with the ability to group similar meal requests together for easier use in meal production planning; this list includes: patient age, physician, diet type, isolation indicator, current diet order and effective date, diet order history, food allergies, preferences, date last seen by dietician, next visit with dietitican, nutritional assessment score, dietitian comments, NPO status
- define site specific recipes - portion sizes, preparation area and time, equipment and serving utensils, recipe category, ingredients, directions for preparation, nutritional values etc
- define multiple meal and menu cycles, including planning for holidays
- forecast meal demands
- access a diet cancellation report for each meal - e.g for patients who have been discharged or passed on. This information should also be updated in the listing of meal requests
- prepare meal distribution lists - for each meal, it should be clear where it is to be delivered, to whom and when. The meals should be accompanied by delivery labels / slips. These slips may be referred to as diet cards or tray tickets.
- access a dashboard / reports with the following information: analysis of served meals, additional meals, cost per meal, tube feeding cost, supplemental feeding cost, staffing etc
- manage inventory and cost of raw ingredients; forecast, requisition, purchase, receive, issue
- access a late admission report / dashboard and notifications - with meal requests arising from admissions that occur close to meal time
- support group ordering e.g meals ordered for seminars
- document and communicate drug-food interaction
3.6.2. Epic: Housekeeping management¶
The housekeeping team cleans and maintains all public and private areas. Some cleaning tasks are scheduled e.g low traffic public areas may be cleaned daily. Some cleaning tasks are performed on demand e.g cleaning spillages in high traffic patient areas or cleaning a room after its occupant is discharged. Sometimes a location may be cleaned on both schedules - every room is cleaned daily, regardless of whether the occupant is discharged or not.
Note
- As a:
- housekeeping supervisor
- I need to:
- maintain schedules for day to day housekeeping activities e.g routine cleaning
- receive notifications for new tasks e.g post-discharge cleaning. These notifications may be from automated events e.g post discharge hooks. They may also be entered manually by nursing staff.
- manually enter and allocate requests for ad-hoc cleaning
- have a dashboard that shows all of the workload, staff and locations in a manner that is easy to process
- maintain cleaning supplies inventory - requisitions, receipts, issues, stock reports etc
- monitor task completion for staff under me
- update task status for staff under me e.g when rooms are cleaned
- mark locations that need prolonged housekeeping work ( e.g wards that are temporarily closed for fumigation ) as unavailable
3.6.3. Epic: Management of central sterile services¶
CSSD coordinates the cleaning / disinfection / sterilization of hospital linen and reusable equipment e.g surgical packs
Note
- As a:
- CSSD supervisor
- I need to:
- define the CSSD store, with items, sets and packs
- define instruments and consumables in each pack
- maintain inventory
- charge user departments for consumption
- generate and print bar code labels for items: name, expiry data, batch number, department / specialty
- autoclaving schedule for all equipment and items
- recognize items consumed in patient care and mark them as due for stelilization
- request for sterilization from outside services
- alerts at CSSD for items due from various points of service
- alerts for items whose expiry date is due for resterilization
- capture broken and lost items
- recall issued items / packs / sets from the user department
- billing for sterilization services
- loaning of equipment to points of consumption
- planned preventative maintenance
- receive contaminated items from wards, outpatient departments and theaters
- exchange those items with clean or sterile ones
- prepare work lists, segregated by sterilization method
- transfer cleaned items to wards, outpatient or surgical departments
- send items to external cleaning agencies
- receive back items from external cleaning agencies
- access a dashboard / reports with inventory, location and transaction information
3.6.4. Epic: Biomedical equipment maintenance¶
Equipment maintenance may be scheduled or ad hoc.
Note
- As a:
- maintenance supervisor
- I need to:
- maintain an equipment-location register, with each piece of equipment uniquely coded
- manage a maintenance schedule
- receive alerts for ad-hoc maintenance requests
- allocate staff for maintenance tasks / issue job cards
- manage external annual maintenance contracts
- request maintenance work from external maintenance partner
- manage warranties - including warranty work job cards
- manage equipment availability for scheduling
3.6.5. Epic: Morgue management¶
Note
- As a:
- morgue manager
- I need to:
- receive bodies - from own hospital and from outside sources ( admission )
- register deaths - including issuance of relevant legal documents
- charge morgue fees - including preservation fees
- manage preservations - work lists
- manage post-mortems - including entry of post-mortem reports
- manage morgue discharge and body collection
- access reports on unclaimed bodies
- dispose off unclaimed bodies - following the due legal process
This particular feature should be designed in a ‘bare bones’ manner.