This repository has been archived by the owner on May 7, 2024. It is now read-only.
Updated Provenance R4 Resource #1018
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
- Validated/updated all links out to HL7 websites. - yaml file had a lot of examples of double forward-slashes - Validated API behavior matches stated specifications. - Updated Overview Paragraph. - Uppercase'd returned fields list. - Parameter Table and Implementation Notes updates to match current guidelines. - Implementation Notes under the Create section modified to match current guidelines. - Anonymized opc-request-id and X-Request-Id values added for response to Create section. - Added backticks to quite a few elements that should be code
kckeim
requested review from
amcginn,
krycunn,
RicardoCrespo-ora,
cldeitrich,
AlexandruBasarab,
napster235 and
gmodrogan
RicardoCrespo-ora
approved these changes
Nov 16, 2023
cldeitrich
approved these changes
Nov 16, 2023
amcginn
reviewed
Nov 28, 2023
amcginn
reviewed
Nov 28, 2023
amcginn
suggested changes
Nov 28, 2023
|
|
||
| The following [HL7® FHIR® US Core Implementation Guide STU 4.0.0](https://hl7.org/fhir/us/core/STU4/){:target="_blank"} Profiles are supported by this resource: | ||
| This resource supports the following [HL7 FHIR US Core Implementation Guide STU 4.0.0](https://hl7.org/fhir/us/core/STU4/){:target="_blank"} profiles: |
There was a problem hiding this comment.
this change violates the HL7 trademark usage policy. we need to add back the trademark registration mark.
There was a problem hiding this comment.
According to our style guide, we do not use any trademark symbols in our product labeling documentation. This has always been the case when referencing HL7 or FHIR.
Per Oracle guidelines, we do need to include the supplier name before the trademarked term for every reference, but omitting the symbols still applies.
amcginn
reviewed
Nov 28, 2023
amcginn
suggested changes
Nov 28, 2023
amcginn
reviewed
Nov 28, 2023
amcginn
reviewed
Nov 28, 2023
amcginn
reviewed
Nov 28, 2023
|
Updated section examples for you @amcginn
|
|
the last screenshot is... weird that it links only two of them. since we do want those links referenced elsewhere, should we add links to the others? |
I'm going to adjust the list so it doesn't trip up the table generator like it did. |
|
Fixed scopes list: |
amcginn
reviewed
Dec 18, 2023
amcginn
approved these changes
Dec 18, 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.
Several formatting updates in this one, and re-wording of sections to be more descriptive and in a similar style to other resources that were recently updated.
Validated that API calls behave as expected with both the expected and unexpected parameters.
Description
PR Checklist
Old Overview and Fields:
New Overview and Fields:
Old Parameters:
New Parameters:
Old Create Notes:
New Create Notes:
Old Create response:
New Create response:
