search

ehealthplatformstandards / BelgianProfileVersioningStrategy

How will we handle the coexistence of different profile versions for the same resource
0 stars 0 forks source link

Is the profile something we can require? #3

Closed bdc-ehealth closed 1 year ago

bdc-ehealth commented 1 year ago

from #1 @smals-bvv By defining only one endpoint for each resource type we need know the profile and version of the profile for when a client retrieves the information back later in time (when profiles and versions might have changed).

ehealthplatformstandards commented 1 year ago

@smals-bvv : this is a very interesting conversation, you should really read it:

https://chat.fhir.org/#narrow/stream/179247-Security-and-Privacy/topic/Progress.20on.20digital.20signatures.20and.20integrity

bdc-ehealth commented 1 year ago

According to HL7 international, we cannot require the profile (at least they discourage it strongly). In #7 we decided not to interfere with metadata.profile , and create our own extension instead.