Skip to content

FHIR ID handling#654

Open
isaacvetter wants to merge 7 commits intomasterfrom
fhir-id-handling
Open

FHIR ID handling#654
isaacvetter wants to merge 7 commits intomasterfrom
fhir-id-handling

Conversation

@isaacvetter
Copy link
Copy Markdown
Collaborator

No description provided.

Comment thread input/pagecontent/2-5-ReceiveEventNotification.md Outdated
isaacvetter and others added 4 commits October 8, 2025 14:27
tweak formatting (add backticks to first open, capitalize Subscriber) and rework sentence for clarity
From the SHALL phrasing in ReceiveEventNotification, we're saying setting preservesFhirId=`true` is required if you are preserving the FHIR ID. Should we go ahead and make the parameter Required? If not, should we add narrative somewhere to suggest that `preservesFhirId` can be treated as False by default?

(maybe something that can be left to the implementer, too)
--------------------------- | ----------- | ----- | ---
`supportsGetCurrentContext` | Optional | Boolean | `true` or `false` - indicating support for the "[Get Current Context](2-9-GetCurrentContext.html)" API.
`supportsNonCurrentContextUpdates` | Optional | Boolean | `true` or `false` - indicating support for the "[Update Events Outside of Current Context](2-10-ContentSharing.html#experimental-capability--update-events-outside-of-current-context)"
`preservesFhirId` | Required | Boolean | `true` or `false` - indicating that the Hub preserve the FHIR resources' logical FHIR IDs while broadcasting open events. If false, the Hub assigns a different FHIR ID and populates an additional business identifier with the value of the requesting subscriber's FHIR ID. See [Hub Generated FHIR IDs]([url](2-5-ReceiveEventNotification.html#hub-generated-fhir-ids)).
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Collision is always a possibility, it seems like a FHIR ID must always be owned by a single, known system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants