About the idea of using "PlanDefinition"

[AlexisVZ-MDS]

If I understood it well, during the kick-off meeting, José suggested we could use the "PlanDefinition" resource as a possible (inspiration for the) input for (initial) requests to PSS. I just had a quick look at https://hl7.org/fhir/R4/plandefinition.html.

My initial thoughts are

• it refers to FHIR workflow, which is "a more advanced FHIR activity", cf. https://hl7.org/fhir/R4/workflow.html At this stage I would prefer to stick to "basic FHIR" implementations ;-)
• that resource is huge and refers mainly to goals, targets and actions, which imho are not yet widely implemented and used in GP softs
• wouldn't it be better to initially focus on using the caresets "problems", "observations", "allergy/intolerance", etc as input for a PSS request ?

[KarlienHL7Belgium]

it will be further clarified in the next WG meetings as business rules are being finalised

[costateixeira]

@AlexisVZ-MDS Agree partly: Yes to use the normal resources as inputs. that is the way FHIR approaches this.
The plandefinition is not for exchange. Vendors interacting with PSS don't have to create or consume PlanDefinitions.
What implementers have to do is call /PlanDefinition/XXXX/$apply as a generic way to call any service, and avoiding custom operations. That is much better (and sticking to normal FHIR) than a custom operation.

We finally agreed to see some examples of how this is done according to the current guidance in the FHIR community:
https://build.fhir.org/ig/hl7-be/pss/branches/cpg-guidance/functional-overview.html

The PlanDefinitions serve to identify which guidance can we call:
1: GetDiagnoses
2: GetDataToCollect
3. GetRecommendedProcedures