Skip to content
This repository has been archived by the owner on May 7, 2024. It is now read-only.

Commit

Permalink
Updated R4 CarePlan Resource (#981)
Browse files Browse the repository at this point in the history
* Update CarePlan R4

Formatting updates to be consistent across parameter notes, including punctuation, and matching _revinclude to other parameters' styling.

Modified _id parameter to call out the situation where _revinclude can be used as well

* Update care-plan.md

* Update care-plan.md

* Update care-plan.md
  • Loading branch information
kckeim committed Sep 21, 2023
1 parent afa0f7a commit c1c69bb
Showing 1 changed file with 10 additions and 10 deletions.
20 changes: 10 additions & 10 deletions content/millennium/r4/clinical/care-provision/care-plan.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,21 +58,21 @@ _Implementation Notes_
`_id` | See notes | [`token`] | The logical resource id associated with the resource.
`date` | N | [`date`] | Time period plan covers. Example: `date=ge2016&date=le2017 (Jan 1, 2016 - Dec 31, 2017)` or `date=ge2016-08-24T12:00:00.000Z&date=le2017-01-24T12:00:00.000Z`
`patient` | See notes | [`reference`] | Who care plan is for. Example: `patient=12345`
`category` | See notes | [`token`] | The scope of care plan being searched for. Examples: `category=assess-plan`
`category` | See notes | [`token`] | The scope of care plan being searched for. Example: `category=assess-plan`
[`_count`] | N | [`number`] | Number of results per page.
`_revinclude`| No | [`token`] | Provenance resource entries to be returned as part of the bundle. Example:_revinclude=Provenance:target
`_revinclude`| N | [`token`] | Provenance resource entries to be returned as part of the bundle. Example: `_revinclude=Provenance:target`


Notes:

- The `_id` parameter
- May not be provided with any other parameters.
- May not be provided with any other parameters, except for `_revinclude` as indicated below.
- When provided, `_count` is ignored.

- The `date` parameter
- When provided, must use both `ge` and `le` prefixes in the same search
- The lower value must have the `ge` prefix and the higher value must have the `le` prefix
- If date precision must be consistent
- When provided, must use both `ge` and `le` prefixes in the same search.
- The lower value must have the `ge` prefix and the higher value must have the `le` prefix.
- Date precision must be consistent.
- May be combined with the patient and category parameters.

- The `patient` parameter
Expand All @@ -83,11 +83,11 @@ Notes:
- Only supports the code `assess-plan`.
- This can be combined with the patient parameter.

- The `_revinclude` parameter may be provided once with the value `Provenance:target`. Example: `_revinclude=Provenance:target`
- The `_revinclude` parameter
- May be provided once with the value `Provenance:target`. Example: `_revinclude=Provenance:target`
- May be provided with the `_id` or `patient` parameter. Example: `_id=178866310&_revinclude=Provenance:target`

- The `_revinclude` parameter may be provided with the `_id/patient` parameter. Example: `_id=178866310&_revinclude=Provenance:target`

- When `_revinclude` is provided in a request to the closed endpoint, the OAuth2 token must include the `user/Provenance.read` scope. Currently `patient/Provenance.read` is not supported and hence `_revinclude` cannot be utilised for patient persona.
- When `_revinclude` is provided in a request to the closed endpoint, the OAuth2 token must include the `user/Provenance.read` scope. Currently `patient/Provenance.read` is not supported and hence `_revinclude` cannot be utilized for patient persona.

### Headers

Expand Down

0 comments on commit c1c69bb

Please sign in to comment.