Model Purpose Compatibility statuses for EHDS

[coolharsh55]

Based on discussions in #283 the dpv:ReuseCompatibility concept should be extended as eu-ehds:PurposeCompatibility to represent the compatibility of purposes as defined and interpreted within the EU EHDS - in particular from definitions in Article 2 and the obligations under Chapter IV. The specific concepts modelling these are:

• PrimaryUse: (EHDS Art.2-2d) means the processing of electronic health data for the provision of healthcare, in order to assess, maintain or restore the state of health of the natural person to whom those data relate, including the prescription, dispensation and provision of medicinal products and medical devices, as well as for relevant social, administrative or reimbursement services;
• SecondaryUse: (EHDS Art.2-2e) means the processing of electronic health data for the purposes set out in Chapter IV of this Regulation, other than the initial purposes for which they were collected or produced;

These concepts should be accompanied with guidelines on how the interpretation of compatibility works by using DPV concepts, e.g. to test for compatibility, which DPV concepts should be compared.

[coolharsh55]

See reference from @brennanraj in #238 where we should be careful in modelling the EHDS terms so that we separate the notion of "primary/secondary use" as concepts from their implementations under the EHDS which have multiple names, namely:

• MyHealth@EU (Article 23)
  • also known as EHDS1
  • is the interoperability infra for primary use
• HealthData@EU (Article 75)
  • also known as EHDS2
  • is the cross-border infra for secondary use

It is likely that practioners will mix the two i.e. refer both concepts for secondary use and the framework as EHDS2. The DPV's documentation should provide clarification regarding this (and also model EHDS1/EHDS2 accordingly e.g. by adding them in the labels for MyHealth@EU and HealthData@EU respectively).