Minutes

Meeting Venue

Oude Middenweg 55

2491 AC Den Haag

Virtual Meeting Room :Teams

Participants

Jurgen asks whom to invite for the call on the 20th of March at 10:00 am for the MPD workitem.
The work item is about E-Prescription in native FHIR MPD using RESTful concept.
It is a Gemini project and there it is open for HL7 participants.
The publication will also be open for ballot for HL7. The question is which ballot procedure will we follow.
The ballot procedures of HL7 and IHE are different. HL7 is extensive and uses Jira.
Juergen is in favor that the ballot procedure of the hosting organization should prevail.
We will assemble a list of candidate participants and send it to Juergen.
What is the intent of this project on the testing.
The goal of this project is to provide the testscenario's. The role of IHE catalyst is to provide tools, but they need additional funding to make it more extensive.
We need to keep our eyes open for possible prospects for funding. Alexander Berler is also active in searching funding.

Suggestion for the new transactions for UNICOM
Also see presentation
- submit product definitions
- Get medicianal products
- Query matching product
- Retrieve product definition
- Enrich prescription (attributes are added).
  - Are these transactions or is this a logical model for mapping
  - Is it transaction between 2 NCPs?
  - Mapping between CDA and FHIR is being worked on in UNICOM/MyHealth@EU.
- Consult prescription
For Rennes we should limit to 2 transactions. Voting : 0 against, 1 abstain, 8 in favor.
- submit product information.
  - How do we this in FHIR?
  - The Medication resource does not allow complex products like Qlaira. See UNICOM FHIR IG
- consulting product information.
UNICOM is working on logical model for Crossborder Product (see IG link above).
GS1 also have model.GS1 model
Another FHIR resource is MedicationKnowledge.
This model is not realistic model according to Rutt. Does not support complex packages, and references to MedicationDefinition module resources even for pack size.
The third option is the MedicationDefinition module resources
the suggestion is to make a matrix with the attributes in the row and the use cases in the columns.
This would make a decision which FHIR resource more simple. It is important to know how far the users and decision makers are prepared to go and which use cases they want to support. It is strictly not only a decision of the IHE Pharmacy, but also of the policy makers.

Continuation of the discussion of medication list of yesterday.
Discussion on the medication treatment. Do we want to make it visible in the medication list?
The medication treatment are used in certain countries like Switzerland and Netherlands.
The question how this treatment is visualized. In Netherlands we use a medication request.
The diagnosis is important. Some countries do send a diagnosis along, but it is often contstrained by privacy laws. So the diagnosis is optional.
In the ideal world this could multilevel hierarchy, but the realistic point is that no information system can record on more than one level.
Discussion on the two different views on the medication list.
- One is a snapshot of 1 certain care provider. For example a discharge form or a referral document.
- The second is a inquiry by a care provider. This care provider should collect all the raw data and make his own medication profile for himself.
The Estonian medication list prototype can be found here
Current information systems register only one type of medication line. They cannot distinguish a medication request, dispense

or statement yet.

There are basically two kinds of reports.
- One with all the raw material (building blocks)
- One with a special ( National ) flavour which could depend per country.
Discussion on the meaning of statement. A statement is a snapshot in a moment of time.
The Swiss Medication treatment plan is the result of the collection of medication statements.

Continuing with the discussion on the FHIR transactions
IHE Medication profile will be called Medication Overview.(PHARM-MedO)
- transactions contentprovider, contentconsumer.
This track will provide guidelines for constituting an aggregrated view.
Is this then not a whitepaper? It should go one step further and provide tips and tricks.
It provides recommendations that enable IT vendors to create their business intelligence.
Meeting will be organized alternating starting on the 27th March from 11:00-12:30. Biweekly

Repetition of the discussion on the Unicom project.
Juergen will create a new page for the project of MPD on FHIR on the IHE Wiki of the technical committee.
Dates for the next F2F are not finalized yet. Current proposition is the week of July 10th.