Attendees

ListServ / Zulip Discussions

FHIR Maturity

Getting our resources to Level 2 and 3

Have identified several vendors that are using some of our resources which collective use all of our resources. Need to determine specifics of who and what, as well as, what documentation would be required to prove level.

Response from Lloyd: For level 2, the requirement is that in some sort of real or test environment, at least 3 independently developed systems have shared the resource covering at least 80% of the data elements. You can capture the name of the connectathon or just a date and a list of the system vendors if it was done outside of connectathon (e.g. through Argonaut)

Additional information provided by Michelle that can aid in collecting FMM evidence

FHIR Discussion Items

July 18 items

Outstanding July 11 items

CDS Request

The CDS Work Group as part of reconciling ballot comments for the CQF-on-FHIR Ballot has created a resource in FHIR that can be used to describe "templates" for intent resources like MedicationOrder, ProcedureRequest, etc. The resource is called ActivityDefinition (https://hl7-fhir.github.io/activitydefinition.html).

As part of specifying the template for a MedicationOrder, we need to be able to specify the dosageInstruction and dispenseRequest elements. Rather than copying the element from the MedicationOrder resource definition, we are planning on defining a DosageInstruction and a DispenseRequest type that we could reference, rather than duplicating the maintenance of those elements.

Do you have any questions or concerns with this approach? The initial step is just to define the data types based on the MedicationOrder structure and will not involve any changes to the MedicationOrder resource.

Pharmacy WG has some concerns about the fact that CDS may be creating

Action: Melva to Invite CDS to join Pharmacy and invite FMG rep

Outstanding June 13 items

10125 - International Realm Pharmacy extensions Profile

Each resource is supposed to have a core profiles

Action: review the pharmacy-extensions-spreadsheet.xml to determine which should be moved to core - MedicationOrder and Medication Dispense

Outstanding June 6 Items

8783 - Medication order status

Epic is withdrawing the gForge issue due to the recent addition of MedicationOrder.eventHistory.

Action: Marla to follow up with Lloyd to check if workflow will impact this (e.g. removal of MedicationOrder.eventHistory)

Renaming MedicationOrder to MedicationRequest Discussion

Email received July 4, 2016 from Lloyd

The FHIR Workflow task force has been working for almost the past year to come up with guidelines to improve the consistency of how workflow (the process of requesting something to happen and then reporting the results of that request) are handled across all FHIR resources. Its scope encompasses clinical, administrative and financial resources. We've had relatively broad participation in the bi-weekly calls and very broad participation in the face-to-face sessions at HL7 WGMs.

While the project is still testing the recommendations using a variety of use-cases, we are sufficiently confident in the stability of the recommendations, that we voted last week to request all impacted work groups to apply the relevant changes to their resources for inclusion as part of the upcoming STU 3 ballot.

We recognize that the timelines for making this occur are tight. In the event that a work group cannot make the changes requested, we invite them to, at minimum, provide an implementation note highlighting the intention to adjust each affected resource to align with the workflow pattern and to include a hyperlink to the "workflow.html" page. (This page doesn't exist yet, but it will.)

We also recognize that not all of these recommendations will fall into the 80% for all resources. Work groups are asked to do the following for each recommendation:

Apply the recommendation from the FHIR workflow task force as part of core

Create extensions to support those data elements that are relevant but not commonly used by the domain

Indicate that they feel the recommendation should not apply to their resource by posting an email to the fhirworkflow list server indicating why they believe a given recommendation is inappropriate for a given resource.

((The list of resources believed to be impacted by the FHIR Workflow recommendations are provided in the attached spreadsheet. Most of the listed resources are categorized as either a "request" - a resource that indicates a specific intention for something to occur; or an "event" - a resource that represents a specific occurrence that could have been done in response to a request. A few event resources are marked with a question-mark as it's not clear whether they are requested or not. It's possible that one or more resources in the spreadsheet that were not categorized should in fact be listed as a "request" or an "event". Feel free to apply the workflow recommendations to uncategorized resources if you feel they should apply.

In addition to these categorizations, the workflow project calls for the Order and OrderResponse resources to be removed. They are superseded by Task. As well, the scope of ProcessRequest and ProcessResponse should be revised to leverage Task for the purpose of requesting the current state of a resource and for soliciting a state change.

The recommendations are as follows:

Request

Add a note in the introduction section that the resource is a "request" resource from a FHIR workflow perspective, including a hyperlink to workflow.html#request.

Rename the resource to [xxx]Request instead of [xxx]Order (request resources are used for plans, recommendations and proposals, not just orders

Ensure all of the data elements present in the "request" pattern document (attached) are present in the resource, keeping consistency with the naming where possible and adapting definitions to reflect domain-specifics

Ensure the status element for the resource has a terminology that aligns with the "request" states as well. (Note that all statuses related to fulfillment progress are now handled by Task.)

Event

Add a note in the introduction section that the resource is an "event" resource from a FHIR workflow perspective, including a hyperlink to workflow.html#event.

Ensure all of the data elements present in the "request" pattern document (attached) are present in the resource, keeping consistency with the naming where possible and adapting definitions to reflect domain-specifics

Ensure the status element for the resource has a terminology that aligns with the "request" states as well. (Note that all statuses related to fulfillment progress are now handled by Task.)

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

Discussion - July 11 Meeting

John described the change proposed - we can alias resource to include MedicationOrder

Moved by John - seconded by Marla to add note to introduction section to Medication Order Add a note in the introduction section that the resource is a "request" resource from a FHIR workflow perspective, including a hyperlink to workflow.html#request. and to add an implementation note highlighting the intention to adjust each affected resource to align with the workflow pattern and to include a hyperlink to the "workflow.html" page. - 7/0/0 Carried

Action: Melva to update Gforge - complete

Moved by John - seconded by Marla to add note to introduction section to Medication Dispense, MedicationAdministration, MedicationStatement - Add a note in the introduction section that the resource is a "request" resource from a FHIR workflow perspective, including a hyperlink to workflow.html#request. and to add an implementation note highlighting the intention to adjust each affected resource to align with the workflow pattern and to include a hyperlink to the "workflow.html" page. 7/0/0 Carried

Action: Melva to update Gforge - complete

FHIR Workflow Meetings Status

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.