Issue/378 profiles for all resources#379
Merged
Conversation
- Changed version for all resources to 2.0.0. - Added new profiles for all supported resources. - Added new profile for complex type Meta to validate read access tags. - Updated urn:ietf:bcp:13 CodeSystem with latest values from IANA. - Added all old 1.0.0 resources to resources.delete file. - Removed Questionnaire 1.0.0 and 1.5.0 profiles, new 2.0.0 profiles will be the only one supported by DSF 2.0.0. - Changed the profile url for the abstract Task profile from .../task-base to .../task - Changes abstract=true to false in QuestionnaireResponse profile - Resources from existing process plugins will be modified to comply with the Questionnaire 2.0.0 and Task 2.0.0 profiles during deployment and resource already in the database will be modified by startup migration jobs. Needed changes not part of this commit - Fixed min cardinalities for sliced values to be equal to slices min sum
- New Task profile in SnapshotGeneratorImpl for HAPI bug workaround - New log method and addition constructor variants in ValidationSupportRule
- QuestionnairesMigrationJob removes version prefix from profiles and sets "required" property for items with link-ids "business-key" and "user-task-id" to true else to false if Questionnaire had old 1.0.0 profile - StructureDefinitionTaskProfileMigrationJob modifies baseDefinition (task-base -> task), adds structure-definition profile and generates new StructureDefinition snapshots - both migration jobs emit resource updated events - New methods in QuestionnaireDao and StructureDefinitionDao to simplify migration job implementation
- removed Questionnaire 1.0.0 profile related tests
- FHIR resources from v1 plugins are rewritten during resource loading to comply with 2.0.0 profiles - FHIR resource from v2 plugins need to be compliant and are not rewritten
- Default profiles are now enforce during create and update operations (single resources and via transaction/batch bundle). - DefaultProfileProvider is used to add a default DSF profile to a new or to be updated resource if the resource does not already declare a profile supported as on of the default profiles. Some exceptions: Since we do not have a default (non abstract) profile for Task resources, no profile is added. But Task resource will need to have a specialized profile declared to make it past the authorization rule. For Organization resources, the member organization profile is considered the default, parent organizations are allowed if the .../organization-parent profile is self declared. The parent profile is considered a "secondary" default profile. Not added by default, but no other will be enforced if self declared. - Fixed integration tests, where non valid resources where used. - Improved ConformanceService: The CapabilityStatement resource now declared DSF profiles as the rest.resource.profile property the the exception of Task, still declaring the FHIR base profile. The parent organization profile is declared as a rest.resource.supportedProfile same is true for Task profiles from process plugins.
- New option in CommandFactory to disable FHIR resource validation during transaction/batch Bundle execution. - FHIR resource validation disabled for the execution of the internal bundle for the initial data loader on startup. - Modified dsf maven plugin Bundle generator to reinclude self declared profiles. - Refactored DefaultProfileProviderImpl from enum to class, since we do not need the DISABLED, ENABLED variants anymore. - Added default validation code to UpdateCommand for "update as create" path.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
- Added missing override annotations - ActivityDefinition profile now also requires date to be set. MII and DSF plugins have ActivityDefinition.date set. - Added AbstractMetaTagProfileTest and AbstractMetaDataResourceProfileTest as base classes to some tests.
- Added missing override annotation
issue/378_Profiles_for_All_Resources
hhund
added a commit
to datasharingframework/dsf-process-hello-world
that referenced
this pull request
Oct 31, 2025
wetret
added a commit
to datasharingframework/dsf-process-hello-world
that referenced
this pull request
Oct 31, 2025
…sues/DSF-344_additional-data-types * origin/issue/5_Update_to_DSF_2: modifications for datasharingframework/dsf#379 removed not needed repo config initial round of changes for DSF 2.0.0 v1.5.0.0 release v1.5.0.0 release 1.0.0.0 release prepare release 0.9.0 0.6.0 release Update LICENSE
schwzr
approved these changes
Oct 31, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
2.0.0.1.5.0. The even older1.0.0is no longer supported.2.0.0profiles. Resources from v2 plugins are not modified and need written as compliant by developers.closes #378