Docs: [AEA-3932] - Added new statuses to OAS and fleshed out overview. #77
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
MatthewPopat-NHS
changed the title
|
MatthewPopat-NHS
had a problem deploying
to
dev-pr
GitHub Actions
Failure
kris-szlapa
approved these changes
Mar 26, 2024
omarisgreat
reviewed
Apr 19, 2024
|
|
||
| It includes some country-specific FHIR extensions, which are built against [FHIR UK Core, specifically [UKcore.stu1 0.5.1](https://simplifier.net/packages/fhir.r4.ukcore.stu1/0.5.1). | ||
| It includes some country-specific FHIR extensions, which are built against FHIR UK Core, specifically [UK Core R4 (v4.0.1)](https://simplifier.net/HL7FHIRUKCoreR4/). |
There was a problem hiding this comment.
The UK Core version is not 4.0.1 (that is the international version). The UKCore version currently published is UK Core STU2 v1.1.3
|
|
||
| You do not need to know much about FHIR to use this API. The API only supports GET requests and the responses will be FHIR. | ||
| You do not need to know much about FHIR to use this API. The API only supports POST requests containing FHIR messages. |
There was a problem hiding this comment.
Remove reference to messages (as this has a different connotation in FHIR). Instead use 'POST requests containing FHIR transactions' (or FHIR resources)
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.
Summary
Remove items from this list if they are not relevant. Remove this line once this has been done
Details
Add any summary information of what is in the change. Remove this line if you have nothing to add.
Pull Request Naming
Pull requests should be named using the following format:
Tag can be one of:
Fix- for a bug fix. (Patch release)Update- either for a backwards-compatible enhancement or for a rule change that adds reported problems. (Patch release)New- implemented a new feature. (Minor release)Breaking- for a backwards-incompatible enhancement or feature. (Major release)Docs- changes to documentation only. (Patch release)Build- changes to build process only. (No release)Upgrade- for a dependency upgrade. (Patch release)Chore- for refactoring, adding tests, etc. (anything that isn't user-facing). (Patch release)If the current release is x.y.z then
Correct tagging is necessary for our automated versioning and release process (Release).
The description of your pull request will be used as the commit message for the merge, and also be included in the changelog. Please ensure that your title is sufficiently descriptive.
Rerunning Checks
If you need to rename your pull request, you can restart the checks by either:
git commit --allow-empty -m 'trigger build' git pushRerunning the checks from within the pull request will not use the updated title.