Reduce ipa dependencies #138
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
mikajylha
reviewed
Jun 29, 2023
Fine-tune TURVAKIELTO text
|
I did not come up with a lot of other content after all. |
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.
mikajylha
requested changes
Aug 7, 2023
input/pagecontent/StructureDefinition-fi-base-patient-medication-request-intro.md
Show resolved
Hide resolved
mikajylha
approved these changes
Aug 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add generic profiles for
MedicationandMedicationRequestfor Kela's use case where they cannot use the IPA dependent profiles (becauseMedication.codeis mandatory there, and in Kela's use case they may not have it available).