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

SOE "Sequence of events" table needed for linking resources to FHIR Encounter #74

Closed
comorbidity opened this issue Jul 6, 2023 · 3 comments · May be fixed by #85
Closed

SOE "Sequence of events" table needed for linking resources to FHIR Encounter #74

comorbidity opened this issue Jul 6, 2023 · 3 comments · May be fixed by #85
Assignees

Comments

@comorbidity
Copy link
Contributor

EPIC Condition.encounter is OPTIONAL
UCDavis screenshare is true, this would be a curveball. Likely means I will update CORE to find “encounter.diagnosis” and/or “condition.encounter”
http://hl7.org/fhir/r4/condition-definitions.html#Condition.encounter
https://build.fhir.org/encounter-definitions.html#Encounter.diagnosis

@dogversioning noted this is true in FHIR spec as well.

@comorbidity comorbidity self-assigned this Jul 6, 2023
@comorbidity
Copy link
Contributor Author

CORE linking of encounter_ref and subject_ref is a 🛑 blocker for progress on many/most things
Applies to
FHR Condition 13% of Cerner
FHIR Medication (Cerner rare, Epic common)
FHIR Observation (Cerner rare )

Likely will invoke building the common “SOE” (Sequence of events) table in health studies
Condition.recordeddate is between Encounter.period.start and Encounter.period.end
MedicationRequest.authoredOn is between Encounter.period.start and Encounter.period.end

@comorbidity comorbidity changed the title Major: Condition Encounter linking can be bi-directional SOE "Sequence of events" table needed for linking resources to FHIR Encounter Jul 11, 2023
@comorbidity
Copy link
Contributor Author

COUNT report for each FHIR resource type having or lacking linkages in SOE

@comorbidity comorbidity linked a pull request Jul 21, 2023 that will close this issue
@dogversioning
Copy link
Contributor

resolved via #85

@dogversioning dogversioning modified the milestone: 2.2 Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants