This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "201801 Pharmacogenomics CDS"

From HL7Wiki
Jump to navigation Jump to search
Line 46: Line 46:
  
 
===Scenario Step 1 Name===
 
===Scenario Step 1 Name===
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
+
:Action:  
:Precondition: <!-- What setup is required prior to executing this step? -->
+
(EHR) Manually enter an order for "Imuran 50mg 1 tablet twice a day by mouth" into order entry system. This triggers a “medication-prescribe” CDS hook with a hook context of MedicationOrder which includes RxNorm code 197388 for azathioprine 50mg oral tablet.
:Success Criteria: <!-- How will the participants know if the test was successful? -->
 
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
 
  
<!-- Provide a description of each task -->
+
(PGx CDS Service) Having been triggered by the “medication-prescribe” CDS hook, the PGx CDS Service now executes a decision support rule that [1] determines if the ordered drug has a known gene interaction; [2] determines, where there is a known drug-gene interaction, whether or not the patient has genetic test results on file; [3] determines, where there are genetic test results on file, if the patient has an interacting genotype; [4] determines, where there are not genetic test results on file, if the patient needs pre-testing. PGx CDS Service returns a CDS hooks “information card” back to the EHR, with appropriate recommendations.
 +
 
 +
:Precondition: Genomic observation(s) are available for some patients.
 +
 
 +
:Success Criteria: Retrieve relevant observations (on TPMT gene, on allelic state) where they exist.
 +
 
 +
 
 +
:Bonus point: Different parameters (such as genomic coordinates) can be used for searching.
  
 
==TestScript(s)==
 
==TestScript(s)==

Revision as of 22:52, 24 October 2017


Pharmacogenomics CDS

Submitting WG/Project/Implementer Group

Clinical Genomics WG

Justification

Proposed Track Lead

Bob Dolin (BDolin@Elimu.io)

See Connectathon_Track_Lead_Responsibilities

Expected participants

  • Elimu
  • Cerner
  • Children’s Mercy Hospital

Please contact track lead or post to CG list if you're interested in participating!

Roles

PGx CDS Service

PGx CDS Service will interact with EHR (via CDS Hooks), OMIC Data Store (for genomoic observations), and Terminology Server (for medication value sets).

OMIC Data Store

Will store genomic observations

EHR

Order entry of a medication triggers a “medication-prescribe” CDS hook which invokes the PGx CDS Service and provides it with a FHIR MedicationOrder instance. This FHIR MedicationOrder instance includes RxNorm code 197388 (azathioprine 50mg oral tablet) in MedicationOrder.medicationCodeableConcept.

Terminology Service

The PGx CDS Service will ping the terminology server to see if the ordered drug is in an “Actionable PGx Drug” value set.

Scenarios

Please see detailed storyboard here: https://docs.google.com/document/d/1VqPrf6aaOB8RhSbAq2JYDxZYbDm-RT9DxA0u6-RxYo0/edit

A swim-lane overview of the scenario is here:

PharmacogenomicsCDS.png


Scenario Step 1 Name

Action:

(EHR) Manually enter an order for "Imuran 50mg 1 tablet twice a day by mouth" into order entry system. This triggers a “medication-prescribe” CDS hook with a hook context of MedicationOrder which includes RxNorm code 197388 for azathioprine 50mg oral tablet.

(PGx CDS Service) Having been triggered by the “medication-prescribe” CDS hook, the PGx CDS Service now executes a decision support rule that [1] determines if the ordered drug has a known gene interaction; [2] determines, where there is a known drug-gene interaction, whether or not the patient has genetic test results on file; [3] determines, where there are genetic test results on file, if the patient has an interacting genotype; [4] determines, where there are not genetic test results on file, if the patient needs pre-testing. PGx CDS Service returns a CDS hooks “information card” back to the EHR, with appropriate recommendations.

Precondition: Genomic observation(s) are available for some patients.
Success Criteria: Retrieve relevant observations (on TPMT gene, on allelic state) where they exist.


Bonus point: Different parameters (such as genomic coordinates) can be used for searching.

TestScript(s)

Security and Privacy Considerations