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.

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

Consider how to approach CodeableConcept.text #229

Open
mikix opened this issue Apr 29, 2024 · 1 comment
Open

Consider how to approach CodeableConcept.text #229

mikix opened this issue Apr 29, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@mikix
Copy link
Contributor

mikix commented Apr 29, 2024

When we denormalize CodeableConcepts, how should we approach text?

Scenarios

  1. Coding.display is present but no Concept.text
  2. Coding.display and Concept.text both present
  3. No Coding.display but Concept.text is present
  4. No Codings at all, but Concept.text is present

1 & 2 are probably easy - just use the Coding.display value as the denormalized display.

3 probably doesn't happen that often. But could.

4 happens in Cerner for inline Medications, Device.type, and probably elsewhere. It's not clear yet if EHRs generally offer a dropdown for that kind of situation and/or allow freeform text entry. In which case, the number of unique text strings is huge (a consideration for using this string in a CUBE).

Use cases

  1. What to show in the dashboard as part of the CUBE?
  2. What to offer to studies for inspection? (i.e. do we want to allow display and/or text as columns for studies to try to parse?)
@mikix mikix added the enhancement New feature or request label Apr 29, 2024
@mikix
Copy link
Contributor Author

mikix commented Apr 29, 2024

Current status is that we ignore text right now and always use display

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant