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

Difference between revisions of "2016-03-28 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%" | <!--...")
 
 
(One intermediate revision by the same user not shown)
Line 22: Line 22:
 
=Attendees to be updated=
 
=Attendees to be updated=
 
* Melva Peters (Chair)
 
* Melva Peters (Chair)
 +
* Steven Warman
 +
* Michelle Miller
 +
* John Hatem
 +
* Scott Robertson
  
 
==Agenda Planning ==
 
==Agenda Planning ==
Line 27: Line 31:
  
 
==ListServ==
 
==ListServ==
*  
+
* None
 
 
 
 
  
 
==FHIR Discussion Items ==   
 
==FHIR Discussion Items ==   
Line 46: Line 48:
  
 
===FHIR tracker items to be discussed this week===
 
===FHIR tracker items to be discussed this week===
 +
* Tracker 9763 - increase cardinality of reason on MedicationStatement
 +
** have increased the cardinality on MedicationOrder to 0..*
 +
*** had to change to two attributes with a comment on how to use
 +
*** MedicationOrder - suggested that the comment should be added on the reasonReference back to the reasonCode
 +
*** MedicationOrder - add a comment to say that the two can be used together
 +
** change MedicationStatement to reflect the changes in MedicationOrder for reason
 +
** moved by Scott - seconded by Michelle to change MedicationStatement and to update the comments in MedicationOrder - 4/0/0 - Carried
 +
Action:  Melva to update Gforge and assign to Michelle
 +
* Tracker 7560 - need to confirm if this was done
 +
Action:  Contact Grahame to see if this was done and if it is Pharmacy WG
 +
* Tracker 8476 - Clarification on medicationOrder.dispense.medication vs medicationDispense.medication
 +
** Discussion of whether we need the Dispense.medication - could be an extension
 +
*** Include in the agenda for next week and determine what to do - either remove or add a comment on how to use
 +
Action:  Discuss further on the next call
 
* Tracker 9296 - Consider new statuses (Proposed, Draft, Under Review) for MedicationOrder and MedicationAdministration.
 
* Tracker 9296 - Consider new statuses (Proposed, Draft, Under Review) for MedicationOrder and MedicationAdministration.
 
** discussion of the granularity - have draft already and Proposed is part of workflow discussion
 
** discussion of the granularity - have draft already and Proposed is part of workflow discussion
 
** suggest that we leave as is for now
 
** suggest that we leave as is for now
 
  Action: post a question to the list serve to seek information - John will start the discussion for the question  
 
  Action: post a question to the list serve to seek information - John will start the discussion for the question  
 +
* Tracker 8489 - Medication related indicators - maintenance dose, over the counter
 +
** Leave as "Considered for Future Use" and discuss when we look at formulary requirements
 +
* Tracker 8778 - BSA Related dosing
 +
** discussion of adding the ability to support a maxDosePerAdministration
 +
** we believe that we should add this element
 +
** Moved by John and seconded by Scott to add maxdosePerAdministration as a simpleQuantity to medicationOrder - 4/0/0 Carried
 +
Action:  Followup with Lee on the modelling to confirm
 +
* Tracker 9302 - Include parameters in dosing - "if x happens, decrease dose by y"
 +
** Scott to send wording - consider on a future call
 
* Tracker 9286 and 5827 - Review the need for status on a Medication Resource.   
 
* Tracker 9286 and 5827 - Review the need for status on a Medication Resource.   
 
** Setup a discussion with Lloyd re: modelling for these items before we make a decision
 
** Setup a discussion with Lloyd re: modelling for these items before we make a decision
Line 55: Line 80:
 
** Consider along with 9296
 
** Consider along with 9296
 
* Tracker 8378 and 8276 - consider adding the reason for all statuses changes on MedicationPrescription.
 
* Tracker 8378 and 8276 - consider adding the reason for all statuses changes on MedicationPrescription.
* Tracker 9302 - Include parameters in dosing - "if x happens, decrease dose by y"
 
* Tracker 8778 - BSA Related dosing
 
* Tracker 8489 - Medication related indicators - maintenance dose, over the counter
 
* Tracker 8476 - Clarification on medicationOrder.dispense.medication vs medicationDispense.medication
 
* Tracker 7560 - need to confirm if this was done
 
  
 
=== Renaming MedicationOrder to MedicationRequest Discussion DEFERRED===
 
=== Renaming MedicationOrder to MedicationRequest Discussion DEFERRED===

Latest revision as of 21:03, 28 March 2016

Attendees to be updated

  • Melva Peters (Chair)
  • Steven Warman
  • Michelle Miller
  • John Hatem
  • Scott Robertson

Agenda Planning

  • Will focus on FHIR change requests, qa items, ballot comments for the next 3 meetings in order to try to get some of the FHIR changes managed

ListServ

  • None

FHIR Discussion Items

GROUPINGS

  • A = Dosage Related
  • B = Terminology
  • C = Misc
  • D =
  • E = Examples
  • F = Multiple indications/reason for order
  • G = Status
  • H = Medication Related
  • I = Mappings

FHIR tracker items to be discussed this week

  • Tracker 9763 - increase cardinality of reason on MedicationStatement
    • have increased the cardinality on MedicationOrder to 0..*
      • had to change to two attributes with a comment on how to use
      • MedicationOrder - suggested that the comment should be added on the reasonReference back to the reasonCode
      • MedicationOrder - add a comment to say that the two can be used together
    • change MedicationStatement to reflect the changes in MedicationOrder for reason
    • moved by Scott - seconded by Michelle to change MedicationStatement and to update the comments in MedicationOrder - 4/0/0 - Carried
Action:  Melva to update Gforge and assign to Michelle
  • Tracker 7560 - need to confirm if this was done
Action:  Contact Grahame to see if this was done and if it is Pharmacy WG
  • Tracker 8476 - Clarification on medicationOrder.dispense.medication vs medicationDispense.medication
    • Discussion of whether we need the Dispense.medication - could be an extension
      • Include in the agenda for next week and determine what to do - either remove or add a comment on how to use
Action:  Discuss further on the next call
  • Tracker 9296 - Consider new statuses (Proposed, Draft, Under Review) for MedicationOrder and MedicationAdministration.
    • discussion of the granularity - have draft already and Proposed is part of workflow discussion
    • suggest that we leave as is for now
Action: post a question to the list serve to seek information - John will start the discussion for the question 
  • Tracker 8489 - Medication related indicators - maintenance dose, over the counter
    • Leave as "Considered for Future Use" and discuss when we look at formulary requirements
  • Tracker 8778 - BSA Related dosing
    • discussion of adding the ability to support a maxDosePerAdministration
    • we believe that we should add this element
    • Moved by John and seconded by Scott to add maxdosePerAdministration as a simpleQuantity to medicationOrder - 4/0/0 Carried
Action:  Followup with Lee on the modelling to confirm
  • Tracker 9302 - Include parameters in dosing - "if x happens, decrease dose by y"
    • Scott to send wording - consider on a future call
  • Tracker 9286 and 5827 - Review the need for status on a Medication Resource.
    • Setup a discussion with Lloyd re: modelling for these items before we make a decision
  • Tracker 8783 - Medication Order Status resolution - review the 2 questions in the tracker item.
    • Consider along with 9296
  • Tracker 8378 and 8276 - consider adding the reason for all statuses changes on MedicationPrescription.

Renaming MedicationOrder to MedicationRequest Discussion DEFERRED

  • From January 25 meeting: Lloyd shared the proposal to rename all request type resources to <resource>_Request. Seeking consistent name for all resources and term that encompasses larger swath of types of requests. An element beneath the tag instance would state the particular request, such as 'order'. This impacts the current Pharmacy Medication Order FHIR resource.
 Completed Action: Rx WG to discuss to determine if we agree or not. - agreed (with no vote) to comply with change but not needed to be made yet, per Lloyd
  • Lloyd suggested that we hold off on making the change, if we decide to make the change. Wait for FHIR Infrastructure group to workout additional details before we make the changes. May have impact on how other data elements are name or included.
  • Discussion: If we agree to the change, we'll need to review the description and other content for our resource to ensure that it accurately reflects the usage. This type of change will mean changes for implementers and it may not be as intuitive for implementers.
    • No decision to be made today. Will consider on a future call
 Action: to followup with Lloyd to find out status and/or next steps

NCCN template orders DEFERRED UNTIL APRIL 4, 2016

  • Lee Suprenant requested input on the ChemotherapyOrderTemplates work.
 Action: Lee will document the items that should be targeted for Pharmacy.
  • Lee requests time in the next call for further discussion or a separate call.
  • Lee completed categorization, needs next steps identified for the columns marked as "maybe".
  • On 2/8 - reviewed Lee's categorizations
  • Lee plans to continue to join our calls as we work through the list.
  • John recommended we would through the list before Lee takes the list to the FHIR workgroup.
  • 3/7 - continued to work through the list to determine what group should deal with each item (row).

FHIR Workflow Meetings Status DEFERRED

  • Status - there were no workflow meetings week of March 14th.
  • Discussion of Pharmacy Workflow Mockup (John)
    • Pharmacy has been providing input into the workflow meeting discussions. One suggestion is that Pharmacy create a Pharmacy specific workflow case similar to the one that is being created for lab. This work has not started yet, but John will start working on this in April.

Catalogue PSS

  • Defer further discussions until April conference calls.

[Draft PSS Posting http://lists.hl7.org/read/messages?id=288115#288115]

  • discussion of the timing for this project - Jose raised concerns that this is a priority but Pharmacy is trying to focus on FHIR changes requests for the next few weeks
  • Jose has proposed to take to other work groups for input - Pharmacy indicated that he should not shop around the PSS until he finds a WG to take on this project
  • the project needs more work before it can been submitted for approval

Joint Meeting with ISO/IHE Pharmacy DEFERRED

  • Room is available courtesy of Canada Health Infoway - waiting for a response from Michael Tan

Template Work DEFERRED

  • Kai to let Pharmacy know when ready for review

Other business

Next meeting

  • Monday, April 4, 2016 - Marla (Chair)