Skip to content

2026/09/16-AO-NBRS-4983-IG-1.12.1 - #627

Open
okunadea wants to merge 4 commits into
Implementation-Guide-V1.12.1from
2026/09/16-AO-NBRS-4983-IG-1.12.1
Open

okunadea wants to merge 4 commits into
Implementation-Guide-V1.12.1from
2026/09/16-AO-NBRS-4983-IG-1.12.1

Conversation

@okunadea

Copy link
Copy Markdown
Contributor

NBRS-4983: Update APP5 medication and allergy wording

NBRS-4983: Update APP5 medication and allergy wording
@okunadea
okunadea requested a review from d-dreyer September 16, 2026 11:54
@okunadea
okunadea changed the base branch from develop to Implementation-Guide-V1.12.1 September 16, 2026 12:11
Updated the wording from "MAY be used" to "IS used" to provide clearer guidance on the resource's intended use and reduce ambiguity.
<details>
<summary>> <b class="barslink">MedicationStatement </b></summary>
<p> This resource MAY be used to carry new medication prescribed at the encounter. This SHOULD NOT be used to carry Medication History obtained from external sources.</p>
<p> This resource ***IS*** used to carry new medication prescribed at the encounter. This SHOULD NOT be used to carry Medication History obtained from external sources.</p>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd move the bold from the IS to the "new".

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same update needs to be made here on the allergies, to match the update to the guidance.

Replaced “novel medications” with “medications administered or prescribed during the latest assessment and not available on existing records”.
Replaced “novel allergies” with “new allergies”.
Updated MedicationStatement guidance from “MAY be used” to “IS used” to clarify the intended use of the resource and remove ambiguity.
@okunadea
okunadea requested a review from d-dreyer September 16, 2026 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants