docs: use neutral entity language for mobile decisions - #98
Closed
abrichr wants to merge 1 commit into
Closed
Conversation
Member
Author
|
Superseded by #102, which is merged and deployed. The canonical page now covers the neutral language rule and its current release status. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Updates shared mobile-decision documentation to use a neutral entity term in the operator-result description.
The shared task schema receives only a qualification-bound static entity class or a neutral
record/itemfallback. It does not infer a domain from live data. The declared OpenEMR fixture remains domain-specific.Validation
git diff --checkuv run mkdocs build --strict