You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
DiagnosticReport.effectiveDateTime
)DiagnosticReport.issued
)Condition.onsetPeriod.start
)And stop there (i.e. no
Condition.onsetPeriod.end
orCondition.abatementDateTime
)Thoughts? This should maybe go in the documentation once we bless it.
The text was updated successfully, but these errors were encountered: