A drug is always prescribed with a particular intent, to act on a condition that is present on the patient (curative, supportive, adjuvant intents) or is feared in the future (preventive intent), or to assess this condition (diagnostic intent)... etc

This treatment intent is generally consistent with a therapeutic indication stated for the drug in its Summary of Prodcut Characteristics (SmPC)

MedicationKnowledge resource captures the therapeutic indication with the associated treatment intent in its indicationGuideline backbone. However, its grand-child element treatmentIntent is not  bound yet to any ValueSet.

On the other hand, MedicationRequest may convey in its reason element the health problem  targetted by this prescription, but is not able to state explicitly what the treatment intent is (curative, supportive, preventive, diagnostic, forensic ...). And yet, this intent is needed, for instance, by a CDS invoked to control the accuracy of the prescription with the available knowledge for this drug (provided by MedicationKnowledge).

Hence the request for these changes:

1) Add an element MedicationRequest.treatmentIntent 0..1 CodeableConcept, defined as "the overall intention of the treatment", with an extensible binding to this ValueSet (to be created):

 2) add extensible binding to the same ValueSet to MedicationKnowledge.indicationGuideline.dosingGuideline.treatmentIntent.

See discussion preluding to this request here:

https://chat.fhir.org/#narrow/stream/179249-Medication/topic/MedicationRequest.20with.20preventive.20intent