Page History
...
| 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