Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update negation text to reflect current common practice in CKM #27

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update negation text to reflect current common practice in CKM #27

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/data_types/master05-text_package.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,7 +199,7 @@ rather than a name. For example, in any `ENTRY` describing current problems, the
the name/value pair "allergies: NONE". Here, "allergies" will be a `DV_CODED_TEXT`, and "NONE"
will be either a `DV_CODED_TEXT` or a `DV_TEXT`; the two will be associated by a containing object,
such as an instance of the `ELEMENT` class from the EHR RM. There is no explicit model of negation
in openEHR.
in the openEHR Reference Model; rather it's usually solved by specific 'exclusion' entry archetypes.
Copy link
Contributor

Choose a reason for hiding this comment

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

in the openEHR Reference Model. Negation statements are normally solved by specific 'exclusion' archetypes.


=== Mappings

Expand Down