Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Avoid making your symptoms & diagnoses concepts boolean; rather, use datatype N/A for these and use them as answers (not questions).  This promotes re-use of these concepts.
    • POOR DESIGN: a boolean "HIV" concept answered yes/no based on whether or not the patient has HIV.
    • GOOD DESIGN: a coded  "DIAGNOSES" or "PROBLEM ADDED" concept that is answered with the concept HIV (the HIV concept has datatype N/A).

Concept naming

  • Always work with your end users to ensure the your concept names make sense to them and match their workflows.

Modeling diagnoses

Here are some notes/conversations related to concept modeling that may be helpful resources when confronting modeling issues.

...

CON
requires search for multiple concepts (could be facilitated by concept_set)

Others Tips

  • Always work with your end users to ensure the your concept names make sense to them and match their workflows.

...

Additional information