Updates to Pharmacy Healthcare Specialty Codes: Updated the display values for specialty codes 60, 70, 80, 90, and 100 to include their definitions directly in the display text. This change applies to CodeSystem-PharmacyHealthcareSpecialtyCS.json and PharmacyHealthcareServiceSpecialtyCS.fsh. [1] [2] Removal of Unused Value Set: Removed the value set http://ihe-d.de/ValueSets/IHEXDShealthcareFacilityTypeCodePatientRelatedHealthcare from HealthcareServiceCategoryCodes as it is no longer used or needed. Documentation Updates: Updated the changelog.md to reflect the changes in specialty codes and the removal of the unused value set.

Updated Slicing on Observation.code & ServiceRequest.code

Assets Updated: - Extension-England-TypedPeriod - CodeSystem-England-PeriodType - ValueSet-England-PeriodType New Assets Created: - CodeSystem-England-ConsentType - ValueSet-England-Consent-Type

- Refactored project structure

- Missing content in ValueSet CompositionSectionCode corrected -- ValueSet re-filenamed CareConnect-CodeSystem-CompositionSectionCode.xml -- CodeSystem re-filenamed CareConnect-CodeSystem-RecordStandardHeadings.xml - Forge StructureDefinition updates - These are modifications to the technical/structural content of the profile and have no bearing on clinical/business semantics - CareConnect-GPC-Practitioner-1 Practitioner.name family cardinality revert 0..1 to 1..1

תיקון מיקום סלייסינג

**feat:** Update dependency to emiga.common to latest version 1.2.0-alpha.7 rki.emiga.vzd/sushi-config.yaml **feat:** Update Examples to match new profile requirements Examples/EpiWarnHealthcareService.json Examples/HospitalRoomLocation.json Examples/InekEinrichtung01.json Examples/InekEinrichtung02.json Examples/InekKrankenhaus.json Examples/InekStandort.json **feat:** Add cardinality 1..* on identifier StructureDefinitions/EmigaDepartmentOrganization.json **feat:** Add extenion for postal address, add cardinality 1..* on identifier, iterate meta.profile version to current -alpha.6 version StructureDefinitions/EmigaHospitalLocation.json **feat:** Add MS on meta.profile for all StructureDefinitions rulesets.json **feat:** Iterate meta.profile version to current alpha.6 version StructureDefinitions/EmigaHealthcareService.json **feat:** Add physicalType code "wa", add 1..* cardinality on identifier, iterate meta.profile version to current alpha.6 version StructureDefinitions/EmigaHospitalFacilityLocation.json **feat:** Add 1..* cardinality to identifier, iterate meta.profile version to current -alpha.6 StructureDefinitions/EmigaHospitalOrganization.json StructureDefinitions/EmigaHospitalRoomLocation.json **feat:** Add Extension for postal Address for IneK UseCases StructureDefinitions/ExtensionInekPostalAddress.json **feat:** Add ValueSet ValueSet/AddressTypePhysicalBoth.json **fix:** Add codes in CodeSystem, remove from ValueSet CodeSystem/IneKFacilityType.json ValueSet/IneKFacilityType.json

**feat:** Iterate meta.profile version to current package -alpha.7 Examples/BundleBatchRead.json Examples/BundleCollection.json Examples/BundleTransactionCreate.json Examples/Communication-441557618.json Examples/DocumentReference-441557619.json Examples/DocumentReference-441557620.json Questionnaire/AdditionalPropertiesQuestionnaire.json Questionnaire/FilingNote.json StructureDefinitions/AnnotationBundle.json StructureDefinitions/AnnotationCommunication.json StructureDefinitions/AttachmentDocumentReference.json StructureDefinitions/EmigaUserPractitioner.json **fix:** Adjust code and display name. iterate CS version CodeSystem/Relevance.json

CA Core 1.0.1 Release Notes AllergyIntolerance • clinicalStatus • Added multiple code systems and value set bindings. • Removed 1.. constraint from clinicalStatus.coding. • verificationStatus • Removed 1..* constraint. • reaction.manifestation.coding • Removed Must Support (MS). • onset[x], onsetDateTime • Added Must Support (MS). ⸻ Condition • code.coding • Removed Must Support (MS). ⸻ Encounter • type, type.coding, type.coding.code • Relaxed cardinality to 0..*; removed MS. • period.end • Added Must Support (MS). • partOf • Relaxed to allow referencing any Encounter, not just Core ones. ⸻ ExampleScenario • Added ExampleScenario resource to illustrate patient scenarios. ⸻ FamilyMemberHistory • condition.onset • Allowed all base FHIR datatypes. ⸻ Immunization • vaccineCode.coding • Removed 1..1 and MS constraints. ⸻ Medication • extension.strength • Added new extension. ⸻ MedicationRequest • statusReason, authoredOn • Removed Must Support (MS). • extension.RenderedDosageInstruction • Added new extension. • Deleted extra whitespace in profile file. ⸻ MedicationStatement • medicationCodeableConcept.coding.display • Changed cardinality from 1..1 to 0..1. ⸻ Patient • Identifier slices (JHN, MRN) • Improved rendering of type, system, and value. • deceased[x] • Removed Must Support (MS). • name.use • Relaxed to 0..1. • communication.language • Changed binding from CommonLanguages (preferred) to iso639-3 (preferred). • extension.communicationBarrier • Removed Must Support (MS) to align with CA:eReC July 2025 block vote (issue #156). ⸻ PractitionerRole • Invariant • Added invariant requiring at least one of: practitioner, organization, or code. • telecom.value • Set to 1..1 with MS. • Later removed MS (temporarily, per issue notes). ⸻ Procedure • code.coding • Removed constraint. ⸻ ServiceRequest • reasonCode • Removed constraints except for HealthConditionCode. • performer • Relaxed cardinality to 0..*. • doNotPerform • Set cardinality to 0..0. ⸻ General / Cross-Cutting • Data Absent Reason Extensions • Removed explicit extensions as per Working Group guidance. • CodeableConcept.text • Added Must Support (MS); flagged for future obligation guidance. • Versioning • Added version numbers to all resources via ruleset for validation and Simplifier. • Aliases • Updated to support new value sets. • Miscellaneous • Applied updates from CA Core+ Simplifier Issue Log: • Issues: #6, #12, #16, #24, #44, #61, #108, #109, #112, #129, #136, #149, #150, #156 • Aligned several changes with PSCA gap sheet.

added Immunization profile

Die Release Notes sind im [Implementation Guide](https://simplifier.net/guide/Implementierungsleitfaden-Terminschnittstelle-fuer-Dritte/Terminschnittstelle-f%C3%BCr-Dritte/Release-Notes?version=2.0.0) zu finden.