Search


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Template Notes

This section outlines the key use cases supported by the work delivered in this project.

It describes the ways in which a user (clinician, information manager, or other) interacts with a system, and it presents the expected behaviors of a system that applies the solutions (methods, model, subsets etc.) that are outcomes of this project.

This section should focus on the benefits that the systems are intended to provide, or the tasks that they are intended to support - more than focus on describing system functionalities.


Notes on target audience for this chapter:

  • All audiences described for this guide should be able to read this section to understand how the deliverables of this work is expected to work.


Epic: Avoiding Repeated Allergic, Hypersensitive, and Intolerance Reactions

Proposal: ALO and ARH

A patient who suffers from an allergic, hypersensitive, or intolerant reaction or disposition with a known cause should be protected by the healthcare providers from any repetitions of these episodes.

Healthcare professionals at the point of care should have access to known allergic, hypersensitive, or intolerant reactions or dispositions in the clinical record. Health information systems should share this information and implement systems to alert the healthcare team of possible risks automatically.

Allergic, hypersensitive, and intolerant reactions can be avoided by preventing the prescription or administration of known trigger substances. The proper documentation of known allergic, hypersensitivity, or intolerance episodes is critical to making this knowledge available at the point of care and supporting decision-making that would prevent future situations. Information needs to be recorded with the right level of detail and context to support these processes.

Use Case 1: Documentation of Information Related to Allergy, Hypersensitivity, and Intolerance


The Following scenarios are copied from the source document with exclusion of FHIR examples. Consider shortening and clarifying to emphasize the intended use case.

Scenario 1.1: Documentation of an adverse reaction to a drug substance

<Add general use case description>

Example

A physician sees a patient in clinic for routine outpatient care.  Recently the patient was prescribed penicillin V 500 mg orally two times daily x 10 days for streptococcal pharyngitis. He tells the physician that he has developed hives the previous week and on examination, the physician confirms the presence of generalized hives. He records this in the patient record as an Observation.

A review of systems fails to reveal any other causes and the physician believes that the patient may be having an urticarial reaction to penicillin. He has lingering uncertainty about this and tells the patient to stop the penicillin and employ diphenhydramine for relief. He schedules him back in a week for follow-up and when recording his note for the visit, he adds to his assessment in the problem list: “Moderate urticarial reaction, possible penicillin allergy”.

A week later, the patient returns for follow-up with the itching and rash entirely resolved.  He reports that the reaction subsided within days after stopping the penicillin.  The physician adds “Penicillin allergy probable: moderate reaction of hives; criticality unable-to-assess” to the allergy list.



Scenario 1.2: Documentation of drug allergy in the allergy list and use as alert to provider

<Add general use case description>

Example

Several years later, the patient from scenario 1.1 who has since received an aortic valve replacement is seeing another physician within the organization for consultation on antibiotic prophylaxis for an upcoming dental procedure. The second physician decides that a penicillin class antibiotic is appropriate for the patient.  

When the physician creates an order for amoxicillin 2 g orally as a single dose and commits to the electronic prescription, an alert appears which requires a response by the physician warning him of an allergy history to penicillin. The substance-based alert is generated by the EHR drug-disease interactions software, which uses the Allergy list as a reference. As the patient has not received penicillin class antibiotics for several years, the physician decides to refer the patient to an allergy specialist for clarification of current status of penicillin allergy. 

The specialist performs skin testing for penicillin allergy, the results of which are positive. The patient is confirmed as penicillin allergic and the results of the testing are documented in the patient’s medical record. 

The patient is subsequently prescribed azithromycin for his dental procedure.


Scenario 1.3: Documentation of a food intolerance

<Add general use case description>

Example

A 34-year-old female is seen by her primary care provider for complaints of abdominal pain, bloating and change in bowel habits within hours or a few days after ingesting whole wheat bread. In addition, she complains of feeling tired but denies itching rash or wheezing. Those complaints are entered as observations in the EHR.

Due to a family history of celiac disease, tissue transglutaminase IgG and IgA are ordered which are negative. The patient is also referred to a gastroenterologist, who performs an endoscopic biopsy, which is negative for celiac disease. (Both of these examination results can be recorded in the EHR as a FHIR observation using LOINC codes).

The patient is advised to avoid wheat and gluten containing products. An encounter diagnosis of moderate wheat intolerance is documented in the patient’s health record and wheat is entered in the patient’s “allergy” list.


Scenario 1.4: Documentation of animal allergy

<Add general use case description>

Example

A physician sees a patient for the first time in clinic for routine outpatient care.  The patient tells the physician that he has begun to experience asthma symptoms.  The physician runs some blood tests and a series of skin tests, which demonstrate an intense reaction to the house dust mite, Dermatophagoides farinae protein with high IgE antibody levels. 

The patient confirms that his wheezing occurs primarily at home, especially while lying in bed at night. The physician opens the allergy record and documents the allergic propensity to Dermatophagoides farinae protein, criticality and severity of low in the EHR allergy list.


Scenario 1.5: Documentation of allergy to non-medicinal substance cross reacting with a pharmaceutical

<Add general use case description>

Example

A patient’s mother reports to their child’s physician that the child reacts violently to eating peanuts with symptoms that include generalized hives, wheezing and hypotension requiring use of epinephrine for resuscitation.  The physician obtains a blood test which documents high levels of IgE antibody against the Arachis h2 peanut protein which is found in unrefined peanut oil (Arachis oil) - the sensitizing agent for clinical peanut allergy. Ara h2 is associated with a risk of severe reactions to peanut.  The physician records a peanut allergy in the EHR with anaphylaxis, hives and wheezing as reaction symptoms, records a criticality of high and reaction severity of ‘severe’.  

Years later, the youngster is seen by a dermatologist for treatment of acne.  As part of the plan of care, the physician enters an electronic prescription for Isotretinoin capsules.  When the physician commits the order, the EHR software runs allergy cross checking and issues a high priority alert that the capsules contain peanut oil that is not highly refined and therefore may potentially include peanut protein and are contraindicated for the patient.  The physician cancels the order and chooses an alternative preparation.


Scenario 1.6: Documentation of allergic reaction to other non-medicinal substances

<Add general use case description>

Example

A licensed nurse presents to her personal physician for recurring problems of a generalized rash and itching.  She works in an intensive care unit and is constantly handling chemicals, disinfectants, assisting in surgical procedures and performing catheter cares for her patients.  As a part of the health history, she noticed that she had an eruption on her hands after handling latex catheters.  Additionally, she reports a serious allergic reaction to papaya in the past and has been careful in the fruits she eats as a consequence.  The clinician suspects a latex allergy cross-reacting with foodstuffs and orders IgE testing for Hevea latex antibody.  The serology testing is strongly positive and the clinician advises the nurse of his findings with warnings about other foods, which may cross react.  While documenting the clinical encounter, he records a latex allergy in the allergy list.

The EHR software supports selection of foods, chemicals and animal biological products as substances, which may be identified as source substances for an entry onto the allergy list or for recording of an adverse reaction.


Scenario 1.7: Documentation of ‘No Known Allergies’

<Add general use case description>

Example

A nurse is performing an intake examination on a patient that is new to the clinical practice.  As part of the clinical interview, he inquires about medication and other allergies.  The patient reports that she is not allergic to any medications, foods, chemicals or animals.  The nurse opens the ‘allergy list’ in the EHR and documents ‘No known allergies’ which electronically validates that the nurse inquired of the patient and that the history was confirmed negative at the date and time recorded.  This satisfies decision support criteria that allergies be documented before medication orders are written and is encoded in the EHR allergy list as confirmed absence of dispositions to adverse reactions.


Use Case 2:  Sharing of Information Related to Allergy, Hypersensitivity, and Intolerance

<Add general use case description>

Scenario 2.1: Sharing adverse reaction data

<Add general use case description>

Example

The patient from scenario 1.1 is planning a vacation with his family consisting of a cross-country camping trip.  In preparation for travels, he speaks to his physician in hospital A and obtains an electronic summary of his healthcare record on a flash drive for himself, his wife and children. His physician informs him that the summary software includes an electronic ‘reader’ as well as a standard format that can be imported into another EHR for patient care.  Their vacation unfolds happily until, many miles from home the patient experiences an episode of right ear pain and is taken to a local emergency room in hospital B.  He provides the flash drive with his electronic record summary to the emergency room physician whose hospital employs an EHR which can accept FHIR extracted electronic record summaries for integration into the on-site health record system.  The emergency room nurse loads the flash drive and accepts the electronic copy of the problem list, allergies and medication list into the on-site record.  The software extract manages the differences in information model design between EHR vendors by crosschecking the allergy list with information in the problem list and encounter diagnoses.

After an otoscopic exam, the patient is diagnosed with acute otitis media. The emergency room physician enters an electronic order for “875 mg amoxiliin with clavulanate 125 mg orally twice daily”, the drug of choice for acute otitis in adults.  When the physician presses ‘Enter’ to commit the order, a pop-up alert is generated by the EHR with warning that this patient has had an allergic reaction to penicillin and has a high likelihood of cross reacting.  While studying the alert, the physician notes that the supporting information was gleaned from the problem list and allergy list.  The EHR drug interaction software has cross-referenced the chemical composition of amoxillin/ clavulanate and noted amoxiliin to be a penicillin derivative.  The physician decides that the information of penicillin allergy is credible and as the patient has taken cephalosporins in the past without issues, the physician changes his order to Cefuroxime, 500 mg orally twice daily.


Use Case 3:  Supporting the Implementation of Decision Support Systems

<Add general use case description> + example


  • No labels