Difference between revisions of "201801 Pharmacogenomics CDS"
| Line 40: | Line 40: | ||
Please see detailed storyboard: https://docs.google.com/document/d/1VqPrf6aaOB8RhSbAq2JYDxZYbDm-RT9DxA0u6-RxYo0/edit | Please see detailed storyboard: https://docs.google.com/document/d/1VqPrf6aaOB8RhSbAq2JYDxZYbDm-RT9DxA0u6-RxYo0/edit | ||
| − | [[File:PharmacogenomicsCDS.png]] | + | [[File:PharmacogenomicsCDS.png|200px]] |
Revision as of 22:46, 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: https://docs.google.com/document/d/1VqPrf6aaOB8RhSbAq2JYDxZYbDm-RT9DxA0u6-RxYo0/edit
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
