Allergy Intolerance Resource – Model Meaning

Slides:



Advertisements
Similar presentations
Allergies & Intolerance Use Cases HL7 Patient Care Technical Committee Larry McKnight, MD.
Advertisements

Andrea M. Landis, PhD, RN UW LEAH
Electronic Submission of Medical Documentation (esMD) eDoC Administrative Documents Templates for HL7 Orders October 25, 2013.
429 pharmaceutical care Plan Refa’a AlAjmi. Goal of therpay A goal of therapy is the desired response or endpoint that you and your patient want to achieve.
Catalina Martínez-Costa, Stefan Schulz: Ontology-based reinterpretation of the SNOMED CT context model Ontology-based reinterpretation of the SNOMED CT.
Copyright © 2010 Wolters Kluwer Health | Lippincott Williams & Wilkins Introduction to Clinical Pharmacology Chapter 04- The Nursing Process.
Learning objectives:- 1. Introduction. 2. Define health record. 3. Explain types of health record. 4. Mention purposes of health record. 5. List general.
Dr Samah Kotb Lecturer of Biochemistry 1 CLS 432 Dr. Samah Kotb Nasr El-deen Biochemistry Clinical practice CLS 432 Dr. Samah Kotb Nasr.
The Process of Scope and Standards Development
Medical Reports Dr. Nasser Al - Jarallah.
ZIMS With Medical Release 2.0 R2 An overview of the Medical Module in ZIMS and how it impacts the Animal Husbandry (R1) Module 1.
Incident Report By miss.EMAN Objectives At the end of this lecture student will be able : Define incident report List elements of incident report Discuss.
Clinical causality assessment I. Ralph Edwards R.H.B Meyboom.
Why are we learning this? How scientific knowledge (pharmacology, therapeutics) and clinical skills (measuring blood pressure, glucoses, drug information)
Copyright © 2014 Wolters Kluwer Health | Lippincott Williams & Wilkins Nursing Issues: A Call to Political Action Chapter 1.
Privacy vs. Confidentiality.  IRB review of privacy and confidentiality protections is required under the Common Rule and the FDA regulations, as well.
EHRp13 Allergies/ADR MU Perspective. Related MU Requirements Clinical Decision Support – drug-allergy order checks PHR, Clinical Summary, Transition of.
EAE Training EAE Reporting and Assessment Overview DAIDS Regional Training Event, Regulatory Compliance Center Kampala, Uganda, September 2009 DAIDS Regional.
Review of Infoway’s COPD* Use Case for Care Plan Business Requirements Sasha Bojicic, Canada Health Infoway Ron Parker, Canada Health Infoway
Biochemistry Clinical practice CLS 432 Dr. Samah Kotb Lecturer of Biochemistry 2015 Introduction to Quality Control.
Quality Education for a Healthier Scotland Pharmacy Pharmaceutical Care Planning Vocational Training Scheme: Level = Stage 2 Arlene Shaw Specialist Clinical.
Introduction.
CRITICAL THINKING AND THE NURSING PROCESS Entry Into Professional Nursing NRS 101.
Commentary: The HL7 Reference Information Model as the Basis for Interoperability George W. Beeler, Jr. Ph.D. Co-Chair, HL7 Modeling & Methodology.
© 2012 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Design of Clinical Research Studies ASAP Session by: Robert McCarter, ScD Dir. Biostatistics and Informatics, CNMC
Role of Site Investigator Ensure subject safety is protected & well-managed Full compliance with requirements of Good Clinical Practice (GCP) Conduct the.
Presented by Allergy/Intolerance/Adverse Reaction Concept Model HL7 Patient Care WG Discussion Pan Canadian Individual Care Standards Collaborative Working.
SNOMED CT Family of Languages Dr Linda Bird, IHTSDO Implementation Specialist.
IHTSDO Education & Implementation Update Dr Linda Bird Implementation Specialist.
A Proposed Approach to Binding SNOMED CT to HL7 FHIR Dr Linda Bird Senior Implementation Specialist.
Nursing Process n116. The Nursing Process  Assessment  Diagnosis  Planning  Implementing  Evaluating.
Statistics for Managers Using Microsoft® Excel 5th Edition
METHODS SECTION OF A RESEARCH PROPOSAL
clinical standards for health care information
Procedure Note (V3) ** = Required sections
Access to Employee Exposure and Medical Records
FHIR Adverse Event Resource
Documentation and Reporting
Present: Disease Past: Exposure
8. Causality assessment:
Implementation of Clinical Guidelines Author: dr. Martin Rusnák
3. Key definitions Multi-partner training package on active TB drug safety monitoring and management (aDSM) July 2016.
Chapter 2 Supplementary Classification:
Hypersensitivity dispositions as clinical findings
Patient Medical Records
Public Health Reporting – S&I Framework CEDD Overview
Access to Employee Exposure and Medical Records
Chapter 4 Clinical decision making in drug therapy
Strength of Evidence; Empirically Supported Treatments
اصول نگارش پرونده های پزشکی
SERIOUS ADVERSE EVENTS REPORTING
ZIMS With Medical Release 2.0 R2
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
Allergy and Intolerances Project
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List aka DC
Condition Resource - Overview
CIMI Semantic Binding Issue
Patient Care WG Allergy and Intolerances Project
Concepts of Nursing NUR 212
, editor October 8, 2011 DRAFT-D
NIH’S Redefinition of Clinical Trials and Using the New Human Subjects Form Chris Sylvester, M.A. Senior Grant Administrator (AO) Grants and Contracts.
Streamlined Data Collection
Why should we disclose? Patients have the Right to Know
Dr Tim England TICH-2 SAE adjudicator
Pharmacology and the Nurse-Patient Relationship
Introduction to Clinical Pharmacology Chapter 4 The Nursing Process
Patient Care WG Allergy and Intolerances Project
Adverse Event Analysis
Presentation transcript:

Allergy Intolerance Resource – Model Meaning Element SNOMED CT Binding Allergy Intolerance IF (($status != ‘entered-in-error’) AND $substance = (< 105590001 |Substance| OR < 373873005 |Pharmaceutical / biologic product|) AND ($type = ‘intolerance’ OR $type = ‘’) AND ($status != ‘resolved’’)) THEN 413350009 |Finding with explicit context|: 246090004 |Associated finding| = ( 418038007 |Propensity to adverse reactions to substance|: 246075003 |Causative agent| = [[ $substance ]]) 408732007 |Subject relationship context| = 410604004 |Subject of record|, 408731000 |Temporal context| = [[ $TC ]], 408729009 |Finding context| = [[ $FC ]]

Allergy Intolerance Resource – Model Meaning Element SNOMED CT Binding Allergy Intolerance IF (($status != ‘entered-in-error’) AND $substance = (< 105590001 |Substance| OR < 373873005 |Pharmaceutical / biologic product|) AND ($type = ‘intolerance’ OR $type = ‘’) AND ($status = ‘resolved’)) THEN 413350009 |Finding with explicit context|: { 246090004 |Associated finding| = ( 418038007 |Propensity to adverse reactions to substance|: 246075003 |Causative agent| = [[ $substance ]]) 408732007 |Subject relationship context| = 410604004 |Subject of record|, 408731000 |Temporal context| = 410513005 |In the past|, 408729009 |Finding context| = 609412005 |Suspected or known present|}, . . . .

Allergy Intolerance Resource – Model Meaning Element SNOMED CT Binding Allergy Intolerance . . . . { 246090004 |Associated finding| = ( 418038007 |Propensity to adverse reactions to substance|: 246075003 |Causative agent| = [[ $substance ]]) 408732007 |Subject relationship context| = 410604004 |Subject of record|, 408731000 |Temporal context| = 410512000 |Current or specified time|, 408729009 |Finding context| = 410516002 |Known absent|}) ELSEIF ($substance = <373572006 |Clinical finding absent|) THEN [[ $substance ]]

Allergy Intolerance Resource - Assumptions The following maps to SNOMED CT are appropriate: reaction. severity Severity (SV) Mild 410515003 |Mild| Moderate 415684004 |Moderate| Severe 410605003 |Severe| reaction. certainty Finding context (FC) Unlikely 415684004 |Suspected| Likely 410592001 |Probably present| Confirmed 410591008 |Definitely present|

Allergy Intolerance Resource – Model Meaning Element SNOMED CT Binding reaction IF ($reaction.certainty = ‘’) THEN 282100009 |Adverse reaction caused by substance|: 246075003 |Causative agent| = [[ $reaction.substance ]], 246112005 |Severity| = [[ SV ]] 255234002 |After| = (432102000 |Administration of substance|: 363701004 |Direct substance| = [[ $reaction.substance ]], 410675002 |Route of administration| = [[ $reaction.exposureRoute ]] )

Allergy Intolerance Resource – Model Meaning Element SNOMED CT Binding reaction ELSEIF (($reaction.certainty IN (‘unlikely’, ‘likely’, ‘confirmed’)) THEN 413350009 |Finding with explicit context|: 246090004 |Associated finding| = ( 282100009 |Adverse reaction caused by substance|: 246075003 |Causative agent| = [[ $reaction.substance ]], 246112005 |Severity| = [[ SV ]]), 255234002 |After| = (432102000 |Administration of substance|: 363701004 |Direct substance| = [[ $reaction.substance ]], 410675002 |Route of administration| = [[ $reaction.exposureRoute ]] )) 408732007 |Subject relationship context| = 410604004 |Subject of record|, 408731000 |Temporal context| = 410512000 |Current or specified time|, 408729009 |Finding context| = [[ FC ]])

Allergy Intolerance Resource – Model Meaning Element SNOMED CT Binding status 408729009 |Finding context| substance 246075003 |Causative agent| reaction. substance 363701004 |Direct substance| reaction. severity 246112005 |Severity| exposure Route 410675002 |Route of administration|

AllergyIntolerance Resource – Value Sets SNOMED CT Value Sets Allergyintolerance-substance-code Substance-code Manifestation-codes Route-codes Other Value Sets in scope of SNOMED CT Allergy-intolerance-status Allergy-intolerance-type Allergy-intolerance-category Allergy-intolerance-criticality Reaction-event-certainty Reaction-event-severity

Procedure Resource - Overview Used to record details of procedures performed on a patient. A procedure is an activity that is performed with or on a patient as part of the provision of care.

Procedure Resource – Assumptions The procedure was performed on the subject of care The value of ‘status’ maps to procedure context: ‘notPerformed’ (boolean) maps to procedure context: ‘bodySite’ may represent either the |Procedure site – Direct| or the |Procedure site – Indirect|. status Procedure Context (PC) In progress 385651009 |In progress| Aborted 385657008 |Abandoned| Completed 385658003  |Done| notPerformed = TRUE 262008008 |Not performed|

Procedure Resource – Model Meaning EDITTING Element SNOMED CT Binding Procedure IF ($status != ‘entered-in-error’) THEN 129125009 |Procedure with explicit context|: { 363589002 |Associated procedure| = ([[ $code ]] : 363704007 |Procedure site| = [[ $bodySite ]], 363699004 |Direct device| = [[ $focalDevice.manipulated.type ]], 424361007 |Using substance| = [[ IF ($used.code = < 105590001 |Substance|) THEN ($used.code)]]), 424226004 |Using device| = [[ IF ($used.type = < 49062001 |Device|) THEN ($used.type)]]), 408732007 |Subject relationship context| = 410604004 |Subject of record|, 408731000 |Temporal context| = 410512000 |Current or specified time|, 408730004 |Procedure context| = [[ $PC ]]}

Procedure Resource – Model Meaning Element SNOMED CT Binding code 363589002 |Associated procedure| bodySite 363704007 |Procedure site| focalDevice. manipulated. type 363699004 |Direct device| used IF (($used.code = < 105590001 |Substance|) THEN 424361007 |Using substance| ELSEIF (($used.type = < 49062001 |Device|) THEN 424226004 |Using device|

Procedure Resource – Value Sets SNOMED CT Value Sets Procedure-category Procedure-code Procedure-not-performed-reason Body-site Procedure-reason Performer-role Procedure-outcome Condition-code Procedure-followup Other Value Sets in scope of SNOMED CT Procedure-status Device-action Data Element in scope of SNOMED CT notPerformed: Boolean

Goal Resource - Overview Used to express a desired health state or intended objective to be achieved by a subject of care, group or organization over a period or at a specific point of time – e.g. weight loss, restoring an activity of daily living.

Goal Resource – Model Meaning Element SNOMED CT Binding Goal 413350009 |Finding with explicit context|: 246090004 |Associated finding| = 404684003 |Clinical finding|, 408732007 |Subject relationship context| = [[ $SR ]], 408731000 |Temporal context| = 410512000 |Current or specified time|, 408729009 |Finding context| = 410518001|Goal context| LET SR = (IF $subject = ??) status 408730004 |Procedure context| priority 260870009 |Priority| addresses 363702006 |Has focus|

Goal Resource – Value Sets SNOMED CT Value Sets Goal-start-event Other Value Sets in scope of SNOMED CT Goal-status Goal-status-reason Goal-priority

Family Member History Resource - Overview Used to record significant health events and conditions for a particular individual related to the subject.

Family Member History Resource - Assumptions ‘relationship’ is recorded using (or mapped to) SNOMED CT < 125676002 |Person| Values for ‘status’ are: Partial, completed, health unknown When ‘status’ = “health unknown”, no conditions will be recorded.

Family Member History Resource – Model Meaning Element SNOMED CT Binding Family Member History IF (($status = ‘partial’) OR ($status = ‘completed’)) THEN FOR EACH $condition 413350009 |Finding with explicit context|: 246090004 |Associated finding| = [[ $condition.code ]], 408732007 |Subject relationship context| = [[$relationship]], 408731000 |Temporal context| = 410511007 |Current or past (actual)|, 408729009 |Finding context| = 410515003 |Known present| ELSEIF ($status = ‘health-unknown’) 407559004 |Family history unknown|: 408732007 |Subject relationship context| = [[$relationship]]; relationship 408732007 |Subject relationship context| condition. code 246090004 |Associated finding|

Family Member History Resource – Value Sets SNOMED CT Value Sets Family-member Condition-code Condition-outcome Other Value Sets in scope of SNOMED CT Administrative-gender

Specimen Resource - Overview Used to describe a sample used for analysis, and the process for gathering, maintaining and processing the sample.

Specimen Resource – Assumptions ‘collection.method’ and ‘type’ use (or maps to) SNOMED CT The value of 118170007 |Specimen source identity| can be determined from the ‘subject’

Specimen Resource – Model Meaning Element SNOMED CT Binding Specimen 123038009 |Specimen|: 118171006 |Specimen procedure| = [[ $collection.method ]], 118170007 |Specimen source identity| = [[ $SSI ]] , 118169006 |Specimen source topography| = [[ $collection.bodySite ]], 70133003 |Specimen substance| = [[ $type ]]  LET SSI = (IF ($subject = . . . )) type 70133003 |Specimen substance| method 118171006 |Specimen procedure| bodySite 118169006 |Specimen source topography|

Specimen Resource – Value Sets SNOMED CT Value Sets Body-site Specimen-container-type Other Value Sets in scope of SNOMED CT V2/0487 (Specimen type) Specimen-collection-method Specimen-treatment-procedure V2_Additive/Preservative

Questions and Discussions