This beta release introduces the following changes:

• ZIBFHIR-318: In profiles zib-LegalSituation-LegalStatus and zib-LegalSituation-Representation, an indirect mapping is added on Condition.clinicalStatus to zib concepts DateStart and DateStop, with guidance on howto map this to the proper status.
• ZIBFHIR-310: In zib-AdvanceDirective,:
  • the mapping to the living will document has been moved from the Consent.sourceAttachment.data element to Consent.sourceAttachment itself.
  • the guidance on Consent.status that normally only active resources are exchanged has been removed.
• ZIBFHIR-304: The "pattern" data type profiles for references to zib HealthProfessional have been be removed. Their functionality (adding the proper comment) has been replaced by guidance in the profiling guidelines and a QA check.
• ZIBFHIR-301: Pulse Rate regularity and frequency are now profiled independently within distinct Observation profiles. A new panel Observation establishes a link between these related concepts using a .hasMember relation.
• ZIBFHIR-239: The profile and related resources for zib AbilityToPerformMouthcareActivities have been published.
• ZIBFHIR-235: In profile zib-NutritionAdvice, a validation error is solved by a technical fix.
• ZIBFHIR-229: In profile zib-SNAQScore, the definition text of .value[x] about the range has been adjusted according to the erratum of this zib.
• ZIBFHIR-227: The reference to Wound on DeviceUseStatement.reasonReference is moved from the zib-MedicalDevice profile to zib-Wound.Drain.
• ZIBFHIR-212: In zib-MedicalDevice, the references have been removed on .reasonReference to zib-BowelFunction, zib-VisualFunction, zib-HearingFunction, zib-FunctionalOrMentalStatus and zib-Mobility, because there's no causual relationship between this zibs. In all these profiles, add the extension workflow-supportingInfo to refer zib-MedicalDevice.
• ZIBFHIR-209: Code NullFlavor/OTH has been added to ProductTypeCodelijst of zib MedischHulpmiddel.
• ZIBFHIR-203: The profile and related resources for zib TreatmentObjective have been published.
• ZIBFHIR-200: The constraints from zib MUSTScore have been added to the zib-MUSTScore profile.
• ZIBFHIR-192: Where zibs (2020 and 2024) create a derived zib where a required bound value set from the base is restricted but gets an extensible binding, the resulting FHIR profile now interprets this as a minimum additional binding. This has been documented in the profiling guidelines and the existing zib2020 profiles have been adjusted accordingly.
• ZIBFHIR-182: In profile zib-FeedingPatternInfant, data type string has been changed to CodeableConcept on the component feedingSupplement to allow for the exchange of coded feeding supplements as well. The cardinality of the component has been changed from 0..1 to 0..* and the comment refers to the relevent value set of Geboortezorg. Finally, guidance has been added regarding this deviation from the zib.
• ZIBFHIR-179: The zib concept InterpretationHeartRate in zib HeartRate has been moved from a distinct Observation profile to Observation.interpretation in the zib-HeartRate profile.
• ZIBFHIR-163: In profile zib-NutritionAdvice, it has been made possible to accommodate the zib string “Consistency” as structured data. Guidance has been added for receiving systems on how to reconstruct this zib string from the structured data.
• ZIBFHIR-162: The profile for zib Visus (including the erratum) is published in the beta package.
• ZIBFHIR-160: In the CodeSystem resources, the description of property inactive has been adjusted to the description from the HL7 code system.
• ZIBFHIR-65: The profile zib-Pregnancy has been moved from the Condition to the Observation resource.