Minutes - Referral WG 2020-05-28

X participants - Microsoft Teams call

Attendees

• Robin Bosman
• Nick Hermans
• Richard Francken
• Will Van Norel
• Arnaud Lippert
• Karlien Erauw
• Erwin Bellon
• Anne Nerenhausen
• Katleen Smedts

Excused

• Tim Weltens
• Philip Sidgwick
• Philippe Baise

Agenda

• Review of logical model and drafts of implementation guides
• New meeting slot ?

Meeting Minutes

• New meeting timeslot to be defined as CIN people have a conflict due to a recurring meeting: evey other Thursday 4PM to 5PM seems to suit everyone fine, Karlien checks with CIN if this works then reschedules, if not, the meeting is kept at 1PM
• RIZIV will share some information on nursing referrals soon
• Karlien will create a document on the WG's Google drive where WG participants can input their feedback on comments and the artefacts of this WG (f.e. the implementation guide and FHIR logical datamodels). The document has been created here
• The reference to the FHIR implementation guide has been put on the [wiki main page]

• As from here go to Detailed Specifications and then choose "Artifact index"

• Robin shares http://build.fhir.org/ig/hl7-be/hl7-be-fhir-referral-prescription/StructureDefinition-be-model-referralprescription.html
• Referral prescription profile has been designed, see http://build.fhir.org/ig/hl7-be/hl7-be-fhir-referral-prescription/StructureDefinition-be-referralprescription.html

• Differential table shows the restrictions
• An extension for request-StatusReason has already been defined by HL7 int’l

• We need this in Belgium
• Identifier: will be UHMEP identifier, naming system will have to be added : other identifiers will be possible
• Will the eHealth plathform be responsible for the UHMEP platform ? No. RIZIV will, a UHMEP identifie generator will have to be made available

• the "S" in red is a "must support" tag, meaning that if you are able to fill this field, you should fill it and send this field
• Category: some codes are proposed by HL7, ie codes as defined in Snomed CT , if we want to use it, we will have to extend the list ; fixed definition of list is preferred, with an additional text field
• Occurrence: some freedom on how to interpret, period in which the request should be acted upon
• When was a request been executed ? A request is an authorization to do sthg ; when it has been executed, this should be reflected in a procedure or eventually an observation…
• "Mantelzorger" can be referenced by the “Related person" FHIR resource: possible issue as this will not be unique
• Are there any ICD10 codes available for procedures ? RIZIV will check with people from the Belgian terminology center
• Co-signers of requests: how to implement in FHIR ? consent resource seems to be a candidate but it seems limited to the patient’s consent
• Questionaire

• Do we need to agree on the content of the questionnaire in this WG ? do we need to set a questionnaire ? or does it need to reference an existing questionnaire ?
• RIZIV confirms that the questionnaire changes every 2-3 years and will check if there are other questionnaires
• Can key-value pairs offer a solution for the questionnaire ?

• Action points for all: please input your comments in the following document

• action point in particular: request-statusReason – do we expect a list having known reasons (value set or codesystem)