This repository has been archived by the owner on May 7, 2024. It is now read-only.
Updated MedicationStatement DSTU2 Resource #1021
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
- Updated Overview. Reworded and re-spaced. - Uppercasing and punctuation added in a lot of places. Some spacing changes too (e.g. leading spaces) - Validated and/or fixed all existing links. There were quite a few in this one. - Added "info_link" to many lines in the yaml files - Added link over to MedicationOrder in the relevant section - Consolidated disclaimer + errors & outcomes notice - Updated Custom Extensions for clarity - Updated Parameter Table + Implementation Notes to match current standards - Modified Implementation Notes related to Create and Update sections - Removed unnecessary details - Took field-specific details and moved them to the yaml file(s) so they would appear alongside the relevant field-specific data - Added the standard disclaimer for "only mentioned fields are supported" - Added anonymized opc-request-id and x-request-id to the Create and Update response headers
kckeim
requested review from
gmodrogan,
AlexandruBasarab,
napster235,
amcginn,
krycunn,
RicardoCrespo-ora and
cldeitrich
RicardoCrespo-ora
approved these changes
Nov 17, 2023
|
|
||
|
|
||
| Notes: | ||
| _Implementation Notes_ |
There was a problem hiding this comment.
The recommendation between Notes/Implementation Notes from tech writers is to use Notes
cldeitrich
approved these changes
Nov 28, 2023
amcginn
reviewed
Dec 14, 2023
| * [Was or Was Not Taken](https://hl7.org/fhir/DSTU2/medicationstatement-definitions.html#MedicationStatement.wasNotTaken){:target="_blank"} | ||
| * [Date/Time started and ended](https://hl7.org/fhir/DSTU2/medicationstatement-definitions.html#MedicationStatement.effective_x_){:target="_blank"} | ||
| * [Medication](https://hl7.org/fhir/DSTU2/medicationstatement-definitions.html#MedicationStatement.medication_x_){:target="_blank"} | ||
| * [Reference to source MedicationOrder, if applicable](https://hl7.org/fhir/DSTU2/medicationstatement-definitions.html#MedicationStatement.supportingInformation){:target="_blank"} |
There was a problem hiding this comment.
Suggested change
| * [Reference to source MedicationOrder, if applicable](https://hl7.org/fhir/DSTU2/medicationstatement-definitions.html#MedicationStatement.supportingInformation){:target="_blank"} | |
| * [Source MedicationOrder reference](https://hl7.org/fhir/DSTU2/medicationstatement-definitions.html#MedicationStatement.supportingInformation){:target="_blank"} |
amcginn
reviewed
Dec 14, 2023
| @@ -65,21 +71,16 @@ All URLs for custom extensions are defined as `https://fhir-ehr.cerner.com/dstu2 | |||
|
|
|||
| ID | Value\[x] Type | Description | |||
| ---------------------------------|---------------------|------------------------------------------------------------------------------------------- | |||
| `patient-friendly-display` | [`string`] | The display that can be used for this field when producing a view suitable for a patient. | |||
| `medication-statement-category` | [`CodeableConcept`] | The [category] of the order, for example: patientspecified, outpatient, etc. | |||
| `patient-friendly-display` | [`string`] | Extension to MedicationRequest.dosageInstruction. The display name that can be used for this field when producing a view suitable for a patient. | |||
There was a problem hiding this comment.
Suggested change
| `patient-friendly-display` | [`string`] | Extension to MedicationRequest.dosageInstruction. The display name that can be used for this field when producing a view suitable for a patient. | |
| `patient-friendly-display` | [`string`] | Extension to `MedicationRequest.dosageInstruction`. The display name that can be used for this field when producing a view suitable for a patient. |
amcginn
reviewed
Dec 14, 2023
| `patient-friendly-display` | [`string`] | The display that can be used for this field when producing a view suitable for a patient. | ||
| `medication-statement-category` | [`CodeableConcept`] | The [category] of the order, for example: patientspecified, outpatient, etc. | ||
| `patient-friendly-display` | [`string`] | Extension to MedicationRequest.dosageInstruction. The display name that can be used for this field when producing a view suitable for a patient. | ||
| `medication-statement-category` | [`CodeableConcept`] | The [category] of the order, for example: patientspecified, outpatient, and so on. |
There was a problem hiding this comment.
having "and so on" here is redundant since it already says they are examples of values, not the complete set
amcginn
reviewed
Dec 14, 2023
amcginn
approved these changes
Dec 14, 2023
SukeshKonjeti
added a commit
that referenced
this pull request
Feb 2, 2024
* Updated MedicationAdminstration R4 Resource (#1010) * Updated MedicationAdministration DSTU2 Resource (#1011) * Review and Updates to Goal (#1027) * Review and Updates to Communication (#1022) * dstu2 Practitioner updates (#1014) * R4 Practitioner updates (#1015) * Person updates for DSTU2 and R4 (#1009) * StructureDefinition updates (#1012) * Updated Medication Order DSTU2 Resource (#1020) * Updated MedicationStatement DSTU2 Resource (#1021) * Updated MedicationRequest R4 Resource (#1019) * Updated Provenance R4 Resource (#1018) * DSTU 2 Patient updates (#1023) * R4 Patient formatting and standard updates (#1028) * R4 Observation,DocumentReference Documentation Updates (#1031) * R4 Encounter Period StartDateTime Sort Update (#1033) * updated Location type search parameter and examples for physicalType (#1034) * [R4][DiagnosticReport][DocumentReference] support search by _lastUpdated (#1032) * [R4][Immunization] Support search by _lastUpdated (#1029) * R4 Binary Autogen CCD add encounter parameter (#1035) * [R4][Immunization] Documentation Update (#1036)
|
After Deployment: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Had a lot of formatting changes on this one to get it into a similar style to other resources that were recently updated.
Verified/updated links throughout document.
Validated that API calls behave as expected with both the expected and unexpected parameters.
Description
PR Checklist
Old Overview + trailer Notes:
New Overview + trailer Notes:
Example Terminology link fixes - before:
Example Terminology link fixes - after:
Extensions before:
Extensions after:
Parameter Table + notes before:
Parameter Table + notes after:
Uppercasing Retrieve function before:
Uppercasing Retrieve function after:
Create Header before:
Create Header after:
Example
statusfield changes - before:Example
statusfield changes - after:Response changes - before:
After:
Update Details change - before:
Update Details change - after:
