Constrain ehealth-skrs-patient generalPractitioner to 0..1 - #327
Open
jhntrifork wants to merge 1 commit into
Open
Constrain ehealth-skrs-patient generalPractitioner to 0..1#327jhntrifork wants to merge 1 commit into
jhntrifork wants to merge 1 commit into
Conversation
fut-patient now rejects SKRS patient updates carrying more than one generalPractitioner reference, since a citizen only ever has one active GP. The ehealth-skrs-patient profile previously had no cardinality constraint on this element at all (inherited base FHIR's unconstrained 0..*); this brings it in line with both the enforced business rule and the ehealth-patient profile, which already constrains it to 0..1.
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
1 participant
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.
Summary
ehealth-skrs-patienthad no cardinality constraint ongeneralPractitionerat all (inherited base FHIR's unconstrained0..*), even thoughehealth-patient(the canonical stored profile) already constrains it to0..1.updatePatientSKRSoperation now rejects any incoming SKRS patient payload carrying more than onegeneralPractitionerreference (trifork/ehealth#4062), since a citizen only ever has one active GP.