Create BeRelatedPerson

[bdc-ehealth]

• identifier

• relationshiptype (is "wettelijke vertegenwoordiger" a relationshiptype or a practitionertype (cd-hcparty?) - mantelzorger?

• at RSB/RSW, this ('trust person', 'legal representative') is a RelatedPerson and also has impact on the access level.

Create a logical model

[bdc-ehealth]

Also look at: https://chat.fhir.org/#narrow/stream/179166-implementers/topic/FHIR.20relationship.20bet.2E.20a.20patient.20and.20a.20representative

[bdc-ehealth]

relationship to the patient: CodeableConcept family-relationships, and acquaintances (friend, neighbour, ...)
role of the person: CodeableConcept: legal representative, mantel-zorger, ... (should this be in another resource, e.g. Careplan), maybe limited in time.

for elements that are common with patient, can we use the same approach as for patient?

[KarlienHL7Belgium]

update 15 May WG: goal is to make a logical model for Be Related person.
Do we need other elements in this logical model @ all ?

[bdc-ehealth]

WG: we will start by creating a logical model based on these elements.

[KarlienHL7Belgium]

relationship has become mandatory, is unknown part of the valueset: @bdc-ehealth to check and confirm