issues
search
cladteam
/
fhir2omop-pm
Repo for tracking overall FHIR to OMOP mapping project tasks
0
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
US Core Encounter mapping
#22
ShahimEssaid
opened
3 days ago
0
Identifiable Patient Data Storage and PPRL
#21
tursynay
opened
3 weeks ago
1
Demo for OMOP Mapping Leads
#20
tursynay
opened
3 weeks ago
0
Acceptance testing and lessons learned
#19
tursynay
opened
3 weeks ago
0
Transformation pipeline implementation(s).
#18
tursynay
closed
2 weeks ago
0
OMOP Achilles tool for validating data transformed into OMOP CDM
#17
tursynay
opened
3 weeks ago
0
Establish criteria for validating transformed data against OMOP CDM expectations
#16
tursynay
opened
3 weeks ago
3
Identify complex mappings or edge cases
#15
tursynay
opened
3 weeks ago
1
Documentation: Various types of documentation based on needs. Technical, end user, tester, layperson, etc.
#14
tursynay
opened
3 weeks ago
1
Documentation: A spreadsheet for the formal model mapping and other supportive documentation.
#13
tursynay
closed
5 hours ago
1
Understand the representation of identifiers on the FHIR side
#12
tursynay
closed
3 weeks ago
0
Develop a representative dataset to support rapid iteration
#11
tursynay
closed
3 weeks ago
0
Define the pipeline environment and overall architecture
#10
tursynay
closed
5 hours ago
1
FHIR to OMOP vocabulary mapping: Identify which attributes have vocabulary values and what bindings, if any, are specified in FHIR R4 or US Core 3.1.1.
#9
tursynay
closed
5 hours ago
4
FHIR to OMOP vocabulary mapping: HL7 & FHIR specific vocabs (i.e. internal vocabs) need to be identified and mapped to prepare for loading into the OMOP vocab tables.
#8
tursynay
opened
3 weeks ago
3
FHIR to OMOP vocabulary mapping: External vocab mappings mostly provided by Athena
#7
tursynay
closed
3 weeks ago
1
FHIR to OMOP model mapping: Define a set of functions to use in the mappings to abstract away any implementation level details.
#6
tursynay
opened
3 weeks ago
1
FHIR to OMOP model mapping: Value transformations (not code mapping). For example, dates and measurements.
#5
tursynay
closed
5 hours ago
3
FHIR to OMOP model mapping: Field(s) to field(s) mapping and FHIR vocab related information
#4
tursynay
opened
3 weeks ago
1
FHIR to OMOP model mapping: FHIR resource type routing to OMOP tables
#3
tursynay
opened
3 weeks ago
5
Determine Model versions
#2
tursynay
closed
3 weeks ago
1
Enumerate in-scope FHIR resources
#1
tursynay
closed
3 weeks ago
1