Also, add a period to description, so it reads better on the rendered page.

Fix heading numbering. Re-organize headings. Add consistency to how terms are introduced. Add links to TURVAKIELTO (both the value set and the example). The link to valueset renders poorly, though.

We said we're not introducing any terminologies, but now we are...

Mainly the STU note that feedback is appreciated.

How did this ever get here, anyway?
Id should be very widely supported for all resources. But there are cases where it is not required, such as when posting a new resource to a server.
See https://hl7.org/fhir/R4/resource.html#id for details.

Because the IPA profile for medications has constraints that are suitable for patient access use case, but not for all use cases.
This is just one potential approach. We could also use the more fine-grained mechanisms like the Obligations extension or other extensions for indicating conformance to another IG or profile.

We need the generic profiles that can refer to the Medication profile that does not derive from IPA.

Also noting a related article here: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9904180/.

Clarifying test is still required.

Add descriptive text for Medication related resources regarding the patient access and other use cases.

The new profiles don't yet have examples.

Fine-tune TURVAKIELTO text

This reverts commit 1011cf9.

This reverts commit 70ab520.

We don't foresee the need for MedicationStatement or MedicationAdministration where we could not use the IPA profile for Medication, right?

To the profile for the patient access use case

Between the patient access and the non-patient-access use cases.

…finnish-base-profiles into reduce-ipa-dependencies