A system for keeping track of medication data would eventually see these scenarios:
(scenarios --> refer to available data, and what kind of static initial conditions can exist)
- Patient’s medication is inside the same system and follows the basic scenario workflows – prescribed, and validated, dispensed and administered exactly as prescribed. CMPD.
- (Chronic) patient is inside the hospital and all his medication activity is recorded inside the same system and follows the basic scenario workflows – prescribed, and validated, dispensed and administered exactly as prescribed
- (Chronic) patient is inside the hospital and all his medication is inside the same system and follows the basic scenario workflows. In addition, patien has a contrasted exam and a surgery in the hospital.
- (Chronic) patient is inside the hospital and all his medication is inside the same system and follows the basic scenario workflows, but medicaton is replaced in the Pharmacy by an equivalent
- Patient is admitted to new hospital and reports known history to admitting physician
- Patient is admitted to new hospital and history is fetched from community repository
- Patient is admitted to new hospital and history is fetched from community repository, but from wrong patient
- Patient is admitted to new hospital and history is fetched from community repository, patient reports additional medication to admitting physician
- Patient is admitted to new hospital and history is fetched from community repository, patient reports verbal dose changes to admitting physician
- Patient is admitted to a country but his medication history is available in another country
- Patient is admitted to hospital for surgery. Search reveals that there is no current medication, but many years ago, patient took antidepressives that may still affect anesthesia. Complete history for the last X months (for vertain type of medication) is fetched from community repository in another country
- Patient has a new treatment. In one of the therapies, there is a mismatch between the expected treatment start time and the real dispense time.
- Patient has a continued treatment. In one of the therapies, there is a mismatch between the expected treatment start time and the real dispense time.
- Patient is admitted to the hospital. Admitting physician builds the patient’s medication history from all sources and other consumers in the hospital reuse that information.
- Patient is admitted to the hospital with infection. Patient refers previous antibiotic treatment followed correctly, and prescription and dispense data are according to patient’s statement. Antibiogram indicates treatment was not effective, and patient admits that 2 doses were skipped and taken after time.
- Phychiatric patient reports adherence. Physician suspects the opposite.
- Patient is admitted with complications, physician suspects the use of oral contraceptive but patient denies it for cultural reasons.
AND...
A system for keeping track of medication data would eventually be used in these cases:
(use cases --> refer to processing of the data, and what kind of dynamic behaviour can be expected)
- The health authorities decide to investigate the long-term effects of a counterfeit medication. Using unique medication item identification (see ePedigree), the patients that took the counterfeit medication are identified, and this is checked with the condition that was being treated with the medication. The patients are identified and called for a consultation.
- To eradicate H. Pylori, the physician wants to determine the ideal therapy. The physician consults the patient's previous treatments, which shows that a previous protocol was followed by the patient at home. The physician wants to investigate whether the treatment was properly followed, including administration times, to investigate whether there can be some resistance to the previous antibiotics.
I'll later post the features that are required by these use cases.
Real use cases also to follow.
