Page History
...
Scenario 2.1: Sharing adverse reaction data
| Panel | ||
|---|---|---|
| ||
EHR systems should be able to exchange adverse reaction information, allowing the healthcare team to receive alerts even when the information of the previous events was recorded in different systems, organizations, or geographical locations. |
...
| borderStyle | solid |
|---|---|
| title | 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 diagnosis.
...
Electronically-stored allergy, hypersensitivity and intolerance information information should be semantically interoperable to enable sharing of information across system, organization and geographic boundaries.
Use Case 3: Supporting the Implementation of Decision Support Systems
Scenario 3.1: Potential adverse reaction alerts
| Panel | ||||
|---|---|---|---|---|
| ||||
Health Information Systems implementers should be able to adopt knowledge bases or clinical decision support systems that can run alerts detections from existing SNOMED CT data, leveraging the SNOMED CT hierarchies and attributes to compute equivalency and subsumption with the clinical entities recorded in the system's rules. | ||||
| Panel | ||||
| ||||
The health information experts in the hospital in scenario 1.5 considered the value of SNOMED CT when initiating the procurement process for the clinical decision support system. They added the requirement that the knowledge rules should be encoded with SNOMED CT. When the patient is seen in the hospital, and a new prescription for Isotreonin is initiated, the system identifies that peanut oil is one of the excipients for the specific medicinal product using the medicinal product SNOMED CT code. The system also identifies a past event of an allergy to peanuts in the patient's allergy list, with the SNOMED code and attributes, and a knowledge rule in the system identifies the risk of cross-contamination of peanut oil with peanut protein, defining these elements with SNOMED codes. After verifying that the rule matches the same SNOMED CT codes recorded in the EHR, an alert is presented to the practitioner. |
Overview
Content Tools
Apps