* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13381&start=0 13381] We need a way to express <daysAdministeredAmount> and <daysNotAdministeredAmount> in Dosage

*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13044&start=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.

+

*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13043&start=0 13043] Fix performer on MedicationDispense - update description and add role back in with appropriate value set

** 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.

** 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.

+

+

== Order Service Catalogue FHIR Project==

+

* To follow the Order Catalog work, use the following listserv: ordercatalog@lists.hl7.org

** June 19, 2017 - Request of new resource - Catalog Entry is being documented. The big picture view of a Catalog would be the use of a Composition resource that has a reference to a Catalog Entry resource and each Catalog Entry resource has a reference to a Medication resource.

+

** June 26, 2017 - JohnH stated that there is a request from the Catalog team that Pharmacy provide a "logical model" to the Catalog team in a similar manner to that created by the Lab group. JohnH to reach out to JeanD to create this type of model.

** NCCN and other European input to support broad requirements. Specific implementations would constrain as needed

+

* Update from John Hatem

+

** June 19, 2017 - next meeting is Tuesday, June 20. Expect report of progress on the IG in next weeks con call.

+

** June 26, 2017. No report this week.

+

+

==CIMI Pharmacy Model Update==

+

* Update from John Hatem

+

** June 19, 2017 - next meeting is Thursday, June 21. Expect a more detailed report in two weeks about progress of mapping of Pharmacy resources to CIMI logical model.

+

** June 26, 2017 - John H has meet with ClaudeN several times to work on aligning the CIMI Pharmacy model with Pharmacy Medication Request resource. Claude is preparing a presentation to review the work with Pharmacy - current proposed Pharmacy conf call is: July 17, 2017

** Scott will continue to review to assess if Pharmacy requires some content from Chapters 11 or 12.

+

** If others have opinions on this topic, please forward your findings/thoughts to Scott Robertson.

+

* June 26, 2017 update

+

** Scott did not find any issues requiring Pharmacy input. Only open question is whether we can remove this from our Agenda going forward.

+

+

==Action Item List==

+

* June 19, 2017 update

+

** Action item list is being updated. The list now is down to 50 open items. John H will continue to work the list by reviewing the minutes and reaching out to folks to assess if specific items can be closed.

+

** We will continue to review the list in our calls for the next few meetings.

+

* June 26, update. Action item list is down to ~ 30 open items. John H will continue to work the list.

+

+

==Pharmacist Care Plan Project==

+

*June 26, 2017: Scot reported that Pharmacy does NOT have to vote on this work. A call will be scheduled in the future to review this work.

+

+

+

==AOB==

+

+

==Next meeting==

+

* Monday, July 17, 2017 at 1pm Eastern - NOTE, new time for weekly teleconference

Misc (Group = none)

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

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.

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.

Order Service Catalogue FHIR Project

To follow the Order Catalog work, use the following listserv: ordercatalog@lists.hl7.org

June 19, 2017 - Request of new resource - Catalog Entry is being documented. The big picture view of a Catalog would be the use of a Composition resource that has a reference to a Catalog Entry resource and each Catalog Entry resource has a reference to a Medication resource.

June 26, 2017 - JohnH stated that there is a request from the Catalog team that Pharmacy provide a "logical model" to the Catalog team in a similar manner to that created by the Lab group. JohnH to reach out to JeanD to create this type of model.

International Chemotherapy Implementation FHIR IG

NCCN and other European input to support broad requirements. Specific implementations would constrain as needed

Update from John Hatem

June 19, 2017 - next meeting is Tuesday, June 20. Expect report of progress on the IG in next weeks con call.

June 26, 2017. No report this week.

CIMI Pharmacy Model Update

Update from John Hatem

June 19, 2017 - next meeting is Thursday, June 21. Expect a more detailed report in two weeks about progress of mapping of Pharmacy resources to CIMI logical model.

June 26, 2017 - John H has meet with ClaudeN several times to work on aligning the CIMI Pharmacy model with Pharmacy Medication Request resource. Claude is preparing a presentation to review the work with Pharmacy - current proposed Pharmacy conf call is: July 17, 2017

Scott will continue to review to assess if Pharmacy requires some content from Chapters 11 or 12.

If others have opinions on this topic, please forward your findings/thoughts to Scott Robertson.

June 26, 2017 update

Scott did not find any issues requiring Pharmacy input. Only open question is whether we can remove this from our Agenda going forward.

Action Item List

June 19, 2017 update

Action item list is being updated. The list now is down to 50 open items. John H will continue to work the list by reviewing the minutes and reaching out to folks to assess if specific items can be closed.

We will continue to review the list in our calls for the next few meetings.

June 26, update. Action item list is down to ~ 30 open items. John H will continue to work the list.

Pharmacist Care Plan Project

June 26, 2017: Scot reported that Pharmacy does NOT have to vote on this work. A call will be scheduled in the future to review this work.

AOB

Next meeting

Monday, July 17, 2017 at 1pm Eastern - NOTE, new time for weekly teleconference