Details
-
Change Request
-
Status: Gesloten
-
3
-
Resolution: Resolved
-
None
-
Nee
-
Alle
-
FHIR
-
MedMij: none as bsn is not allowed anyway. Other use of FHIR: not backward compatible, but very small risk of impact based on the knowledge that the first occurrence in V3 of an N8 bsn was 15 years after we started with V3.
-
Profiles
-
Document N9 in FHIR where N8 is prefixed with a leading zero.
-
Description
Logisch+Ontwerp+BSN+1.4.pdf says Burgerservicenummer is N8..9 and eleven proof. In order to perform the eleven proof test, you must add a leading zero in case of an 8-digit-BSN.
nl-core-patient does not put any restriction on the value (nor does HL7v2 datatype CX)
HL7v3 II.NL.BSN says to add a leading zero on 8-digit-BSNs and thus always send N9. For elements with datatype II.NL.BSN, there is a coreschematron enforcing this rule and the eleven proof check.
The difference between FHIR and V3 makes for harder mappings, and in FHIR specifically for less clear specifications in case of 8-digit-BSNs.
Proposal:
- Consider adding same N9 restriction/eleven proof check to FHIR as present in V3, or at least document N8..9
- Consider updating ada2fhir and/or hl72ada mapping for BSNs that have a leading zero based on decision in first proposal
- Update ada2hl7 mapping for 8-digit-BSNs to add a leading a zero. See pull request