Minutes - FHIR Validation Group 2020-11-12

Thursday, 12th November 2020, 09:30 CET

Agenda

• Welcome
• Review and Approve Agenda
• Profiles: Candidates for official publication

Participants

• Robin Bosman
• Filoretta Velica
• Karlien Erauw
• Anne Nerenhausen
• Hanne Vuegen

Minutes

Profiles: Candidates for official publication

• Home Care Plan
  • Hanne to send the Project Proposal to the group
• Home Care Team
  • Hanne to send the Project Proposal to the group
• Vaccination
  • We will continue to do a final QA
  • Anne will reach out to Terminology center to ask for proper value sets and translations
  • We discuss that the value sets should be published even if empty (if a value set is not available, we make an empty one ans "draft" and this goes into the backlog of the Terminology team). The binding for these value sets need to be NOT required - extensible.

José to try this out José to update the template for showing "draft" resources in a different color

• AllergyIntolerance Updates
  • as per the process below, this will continue on HL7 Belgium with status = draft.

• Patient Will
  • One issue found (category vs provision.code) - fix example and constraints.
  • Same issue as above with valuesets (for category, we need an empty valueset and in provision.code)
  • This may be impacted by the Déclarations Anticipées Correctes - but we will follow the same process.

• Addiction
  • Same thing with Value Sets
  • add Quantity - it is in the Logical Model but not in the profile
    • will be an extension - "addictionQuantifier" as a Ratio data type (which includes qty per period, and intervals e.g. "2 to 3 packs per day")
  • Add examples

General remark to make sure Introduction text is up to date.

• Problem
  • Same issue - create an empty ValueSet
  • Make sure that all valuesets and codesystems used are NOT marked as complete unless they are actually complete. Codesystem.content can be marked as fragment
  • event.basedOn - is not correct - this should be a way to indicate that there is a prescription/referral in the origin of the finding of the problem (so it would be a relation to an event or encounter) - Conclusion: Replace extension by simply making .encounter Must Support.
  • Update CodeSystem - no values present???
  • add empty valueset for .code
  • add empty valueset for bodysite
  • add translations to laterality

• ScoreResult
  • Update all the codesystem codes - display in English, definition in English. And translations in fr-BE and nl-BE. For now we don't do de-BE.

Lifecycle of profiles between HL7 BE and eHealth

Proposal:

1. HL7 Belgium will publish the profiles with the hl7belgium.org URL
2. When HL7 Belgium requests eHealth to promote the profiles as federal standards,
   1. eHealth takes up the profile
   2. When eHealth completes the publication, HL7 Belgium marks the profile as "retired", and adds a note "This is replaced by a federal standard, please see here (with the link)"
3. If at any point in time HL7 Belgium wants to update the profile, they can change the status again to Draft and continue

This means that HL7 Belgium has profiles in DRAFT mode (work in progress), Retired (taken up as is by eHealth) or Active (in the exceptional case where there is a deliberate difference between HL7 BE and eHealth profile specification.

José to make a simple diagram for this lifecycle

HL7 Belgium Validation Workgroup