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 whether we want to change our current approach to dates #16

Closed
mikix opened this issue May 2, 2024 · 1 comment
Closed

Consider whether we want to change our current approach to dates #16

mikix opened this issue May 2, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@mikix
Copy link
Contributor

mikix commented May 2, 2024

Right now, we have a list of date fields we check in priority order, for when we want to slice by a resource date.

This ticket is just a reminder of our "philosophy" around that priority order and a discussion check-in on whether that approach makes sense.

Here's what we are currently thinking, in highest preference first order:

  1. Date of health system interaction (e.g. DiagnosticReport.effectiveDateTime)
  2. Administrative date (i.e. resource creation date like DiagnosticReport.issued)
  3. Clinically relevant "start" date (e.g. Condition.onsetPeriod.start)

And stop there (i.e. no Condition.onsetPeriod.end or Condition.abatementDateTime)

Thoughts? This should maybe go in the documentation once we bless it.

@mikix mikix added the documentation Improvements or additions to documentation label May 2, 2024
@mikix
Copy link
Contributor Author

mikix commented May 22, 2024

The qualifier repo was recently updated to include .end fields and abatement - just in general, it recommends more fields. And I've got a PR to implement that in #29, so let's consider this considered and close this ticket.

@mikix mikix closed this as completed May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant