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

Difference between revisions of "2017-08-14 Rx Conf Call"

From HL7Wiki
Jump to navigation Jump to search
(Created page with " {| style="width:100%; background-color:transparent;" |- | style="vertical-align:top; width:50%" | <!-- LEFT COLUMN --> __TOC__ | style="vertical-align:top; width:35%" | <!-...")
Line 25: Line 25:
! Name || email || Attend
! Name || email || Attend
| Jean Duteau |||| style="text-align:center;" | x (Scribe)
| Jean Duteau |||| style="text-align:center;" |  
| John Hatem || || style="text-align:center;" | x  (Chair)
| John Hatem || || style="text-align:center;" |  
| Melva Peters || || style="text-align:center;" |   
| Melva Peters || || style="text-align:center;" |   
| Scott Robertson || || style="text-align:center;" |  x
| Scott Robertson || || style="text-align:center;" |   
| Michelle Miller|||| style="text-align:center;" |  
| Michelle Miller|||| style="text-align:center;" |  

Revision as of 18:28, 7 August 2017


Name email Attend
Jean Duteau
John Hatem
Melva Peters
Scott Robertson
Michelle Miller

Agenda Items and notes

CIMI Pharmacy Model Update

  • Update from John Hatem
    • July 17, 2017 - Claude Nanjo provided an overview of the CIMI logical model that incorporates the Pharmacy FHIR resource work. This work will be balloted as Informative in the HL7 September 2017 ballot.
    • July 31, 2017 - concerns raised about how Pharmacy will be involved and be expected to manage the content
      • will be balloted as informative
    • August 7, 2017 - John Hatem is following up with Claude N. on what type of commitment is expected from Pharmacy going forward.

Tracker Items

FHIR Tracker

  • July 31, 2017
    • Use cases - coded product vs non-coded product
      • John will work with others on how detailed we need to provide information on packaging
      • Discussion of when a medication is ordered that is included multiple products; or when medication is order with specific packaging - need to define use cases
Action:  Provide examples of the various medications that we would need to ship around in orders/dispenses/administrations/statements to see what we actually need
Action:  John to coordinate the analysis of packaging information needed for requests, dispenses, administrations and statements - additional attributes that are needed when code is not specific enough
  • August 7, 2017 - John will report on what type of "medication" information is needed in our Pharmacy Medication resource re: Packaging.

Medication Related (Group = A)

  • 13392 Enhance the Medication resource for alignment with the IDMP Authorized Medicinal Product model
  • 12396 Medication package and product

Dosage Related (Group = B)

  • 13381 We need a way to express <daysAdministeredAmount> and <daysNotAdministeredAmount> in Dosage
    • Found non-persuasive as not in the 80% rule. Scott/Jean - 2-0-0
  • 13380 Possible new element in Dosage: calculationBasis
    • Found non-persuasive as not in the 80% rule. Scott/Jean - 2-0-0
    • New tracker item added for MedicationStatement.supportingInformation as we believe it is missing
  • 13317 Allow Dosage to express a medication should start/stop relative to an event
    • use additionalInstruction to convey as text. If needed to be codified, should be an extension/change on Timing datatype. Jean/Scott - 2-0-0
  • 12791 Update dosage Instruction to include pre-condition and therapeutic target
    • confer with group in next call on how this should be done - text vs codified

Misc (Group = none)

  • 13546 Add non-clinical supportingInfo examples
    • Agree to add an example. Scott/Jean - 2-0-0
  • 13044 Fix performer on MedicationAdministration - update description and add role back in with appropriate value set
    • waiting on changes from Workflow
    • Logical model for workflow has Performer (0..*) with roles from SNOMED
    • John - we were asked to constrain that role list but we decided at the time not to include role. Now we want to have it and need it to work with the definition in workflow.
    • Michelle - if role is a static aspect of the performer, then we don't need it (it's available in the specific resource describing that person). We need role if it related to the specific event and may not be consistent across related events.
    • extensive discussion ... does this include performer/verifier? That was previously advised (by FHIR) to be done with provenance. This may result in a "stack" of provenance events related to the order (ordered by, verified by, modified by, ...). This isn't how most systems are designed ... would be extensions(?) ... at least it would work. Event history (links to provenance) doesn't link to the most recent status ... would have to track through the provenance find the most recent state.
    • 6/12 we have not reach the end of this discussion
      • John - the specific tracker can be addressed by adding role to medicationRequest, but this may not address the intent.
  • 13043 Fix performer on MedicationDispense - update description and add role back in with appropriate value set
    • waiting on changes from Workflow
  • 13537 Collapse medicationAdministration.notDone into status
    • we discussed 13537 which is a request to update Medication Administration by removing the NotGiven Boolean and adding in a new status code - not done. Since this is coming from workflow we decided to wait until this is added to the Event logical model for Workflow and evaluate the definition of "not done" and assess it's relevance for Pharmacy. In general there was a positive reaction to this request.
  • 13538 Collapse medicationDispense.notDone into status
    • we discussed 13538 which is a request to update Medication Dispense by removing the notGiven Boolean and adding in a new status code - not done. Since this is coming from workflow we decided to wait until is added to the Event logical model for Workflow, and evaluate the definition of "not done" and assess it's relevance for Pharmacy.
      • Michelle mentioned we may also want to review Patient Care 12592 before we make our changes since there was some discussion about how this change should/should not impact the Request resource.
  • 13384
    • Since FHIR-I does not see the need for a change, we will not be changing. Jean/Scott - 2-0-0

Order Service Catalogue FHIR Project

  • To follow the Order Catalog work, use the following listserv:
  • Background
    • under Orders WG.
    • Catalogue vs Formulary. Catalog is a superset of Formulary, includes orderable items beyond medications.
    • expect one or two new resources
    • Jose and John involved
  • Updates
    • New Lab resource was created. John Hatem will continue to monitor and attend meetings.

International Chemotherapy Implementation FHIR IG

  • Chemotherapy IG Wiki Page
  • Background
    • NCCN and other European input to support broad requirements. Specific implementations would constrain as needed
  • Update from John Hatem
    • Next meeting will be held August 15

Blood Products/Transfusion/Tissue Update

  • Background:
    • based in Patient Care. also includes Orders
    • Blood Products/etc moving into FHIR. Want to maintain alignment with Orders and Pharmacy resources
  • Eric H has sent out a Doodle poll to determine a meeting time for OO, PC and Pharmacy to discuss.
    • Meeting is currently scheduled for Aug 10, 2017

CDA Value Set Updates

  • Don Lloyd sent an email to the Pharmacy WG about reviewing required updates to CDA value sets that are Pharmacy-centric
    • We requested that the spreadsheet mentioned in the email be sent to us so we can review.

Action Item List

  • August 7 update: John is working on cleaning up the action item list


Next meeting

  • Monday, August 21, 2017 at 1pm Eastern - NOTE, new time for weekly teleconference