Some fields must be tagged as "Must Support" and some cardinalities are wrong

[lionel-cremer]

Meta must be marked as Must Support in all profiles

Fields to mark as "Must Support"

• meta (in all profiles)
• meta.profile (in all profiles)
• meta element must support the pseudonymization extension (BeReferral):
  • https://www.ehealth.fgov.be/standards/fhir/infsec/StructureDefinition/be-ext-key-pseudonymization
• this extension must be marked as Must Support as well
• extension:bodyLaterality (BeReferral)
• occurrenceTiming.repeat.period (BeReferral)
• occurrenceTiming.repeat.periodUnit (BeReferral)

Fields where cardinality mus be udpdated

category:prescriptionType must have the cardinality 1..1 (BeReferral)
category:annex81TechnicalType must have the cardinality 1..1 (BeAnnex81)

[costateixeira]

Hello

MustSupport is just for informative purposes, and doesn't change the behaviour at all.
All profiles support pseudonymization already, so I think this may be for a new release - not seeing MS as blocking now.
@lionel-cremer agree to park this for now since it is not blocking?

[lionel-cremer]

We need this now because we use the must support to filter the data in the payload.
We keep only the "must support" fields.
It's a requirement from the DPO.

[costateixeira]

Must Support is not intended to be normative in that sense. While this is hardly an agreed approach, we will put it in the build for now.

…

On Wed, Feb 11, 2026 at 12:30 PM lionel-cremer ***@***.***> wrote: *lionel-cremer* left a comment (hl7-be/referral#484) <#484 (comment)> We need this now because we use the must support to filter the data in the payload. We keep only the "must support" fields. It's a requirement from the DPO. — Reply to this email directly, view it on GitHub <#484 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD3HUUDI4CDBOILEA4POOA34LMHEZAVCNFSM6AAAAACUXIPQRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQOBTHA2DCOBXGM> . You are receiving this because you commented.Message ID: ***@***.***>

[costateixeira]

Why meta MS? What else is must support in meta besides profile?

[lionel-cremer]

The extension for the pseudonymization is required when free-text are present in the resource.
So, I assume it must be marked also as "must support".

Here is an example:

"meta": {
    "extension": [
      {
        "id": "99487e29-c1db-414d-806e-ad6bb8565072",
        "url": "https://www.ehealth.fgov.be/standards/fhir/infsec/StructureDefinition/be-ext-key-pseudonymization",
        "extension": [
          {
            "url": "key",
            "valueString": "urn:be:fgov:pseudo:v2:AgH9nXtR5YCiBbvcgpAyF53znKhx4mGKZUbEgzVqeAo02wj6ut458gtIxqwo6nGanDHqkZKcVGag-o4s1XfRE5J97g:eyJhdWQiOiJ1aG1lcF92MSIsImVuYyI6IkEyNTZHQ00iLCJleHAiOjE3NzA4OTQ1OTAsImlhdCI6MTc3MDgwODE5MCwiYWxnIjoiZGlyIiwia2lkIjoiYWMwNWIzMjktMzhhOS00NTE0LThlMGMtMjI0NTcyOTI4ZWI5In0..qR25W0L0qe38KWIr.Da5okDGda5pDy_ZyZS5ySBiTTIfAa4hhFSwI9JmP7oE8vXiLJTEPk3oo5bN2crCTg_8UhaBcPFzMaHduE8CLZplgkDDgx8xJlwm6emcefgHob1Hn5-69Z8Xg_FBuptf8yBZvZAjS9ks5ZISMQJ0xOvcznWiCU2FZPDECLAWjq_tCfXgkqGQP.G6uJzHgZX9XH-NgN2jH6XA",
            "_valueString": {
              "extension": [
                {
                  "url": "https://www.ehealth.fgov.be/standards/fhir/infsec/StructureDefinition/be-ext-pseudonymization",
                  "extension": [
                    {
                      "url": "marker",
                      "valueBoolean": true
                    },
                    {
                      "url": "format",
                      "valueCode": "direct"
                    },
                    {
                      "url": "version",
                      "valuePositiveInt": 2
                    }
                  ]
                }
              ]
            }
          }
        ]
      }
    ],
    "profile": [
      "https://www.ehealth.fgov.be/standards/fhir/drp/StructureDefinition/be-referral-servicerequest-nursing"
    ]
  },

Note: In case you didn't notice, I updated the issue.

[costateixeira]

meta.profile will be MS. but why does meta need to be MS?

[costateixeira]

To make the category 1..1 - can you make a separate ticket? just because that one will depend on updating all the examples, while this one is easier to update

[costateixeira]

Looking at the business impact of making meta.profile MS - this would mean that meta.profile would be in the logical model (our rule is: MS are the elements for which we functionally care, so they are in the model). While adding meta.profile as MS could be OK (harmless) it would imply that other profiles would have the same approach, and that is not a change we can accommodate. Technically it is a simple change, but the impact is uncertain.

[costateixeira]

Pending business approval given possible impact and setting a (unclear or poor) example. But you can add it on your local structuredefinition.