Observational Health Data Sciences and Informatics documentation:next_cdm

documentation:next_cdm:add_person_to_cost

Anonymous (anonymous@undisclosed.example.com) — 2017-07-10T16:43:01+0000

Cost Table Changes (Add Person_id, Dates and normalize) Proposals are now being tracked as github issues link to github issue Proposal Owner: Gowtham Rao, Chris Knoll, Klaus Bonadt Discussion: Cost table description: Proposal overview: * Add person_id * Add billed_datetime and paid_datetime

documentation:next_cdm:add_survey

Anonymous (anonymous@undisclosed.example.com) — 2017-08-01T18:08:07+0000

Adding PROM data to CDM Proposals now housed on github link to github * Requestor: Colin Orr and Catherine Kerr, ICON plc * Revising party: Joshua Ransom, Anna Corning, Emelly Rusli, Rayhnuma Ahmed, Aaron Stern; SHYFT Analytics * Discussion: here Background

documentation:next_cdm:add_time

Anonymous (anonymous@undisclosed.example.com) — 2015-12-21T03:22:55+0000

Add Time Field to Occurrence and Exposure Tables While v5 visit_occurrence table supports both date and time of event, other occurrence tables and exposure tables such as drug, condition, and procedure support only the date level. It is desirable to have the option to include specific time data for such occurrences.

documentation:next_cdm:cdm_process

Anonymous (anonymous@undisclosed.example.com) — 2017-08-04T14:05:47+0000

Process for adopting CDM/Vocabulary changes Discussing proposals Proposals are discussed either: * on the github issue site * during the workgroup meetings * or on the OHDSI Forum for CDM Builders Submitting proposals Proposals were previously submitted at the CDM and Vocabulary Development. From 7/11/2017 forward they are submitted as issues on the CDM

documentation:next_cdm:clinical_trial

Anonymous (anonymous@undisclosed.example.com) — 2017-01-13T18:07:42+0000

Understanding Role / Relevance of Clinical Trial Data in the CDM Proposing person: Vojtech Huser (someone initially posted this to the wiki (not indicating the source), I got assigned to it) Forum thread: Use Case(s): 1. observational trial collects CRF data but also wants to digest any EHR updates (e.g., AllOfUs project)

documentation:next_cdm:concept_sets

Anonymous (anonymous@undisclosed.example.com) — 2017-03-04T13:37:59+0000

Representing Visits, mini-visits, micro-visits, encounters and claims in OMOP CDM * Requester: Gowtham Rao * Background and problem statement: A person’s care journey over time is represented in the visit_occurrence table of the OMOP common data model. Visit_occurrence table represents this journey as span’s of time a person continuously receives medical services from one or more providers at a care_site in a given setting within a health care system. The unit of representation in visit_occ…

documentation:next_cdm:conditionstatus

Anonymous (anonymous@undisclosed.example.com) — 2017-07-13T17:30:18+0000

Proposal Proposals are now tracked as github issues github issue [Discussion]

documentation:next_cdm:country

Anonymous (anonymous@undisclosed.example.com) — 2017-08-02T13:46:28+0000

Add country field in LOCATION table Proposals are now housed on github link to github issue * Requester: Ajit Londhe * Discussion: here. ---------- Proposal The CDM’s Location table includes physical location fields such as street address, state, zip code, and county. However, there is no field for capturing the country of the subjects.

documentation:next_cdm:data_provenance

Anonymous (anonymous@undisclosed.example.com) — 2016-01-13T16:41:32+0000

Data Provenance * Requestor(s): Daniella Meeker This topic requires more specificity (i.e. are we talking about each datum, entire OMOP instance, what?). Consider folding this into the notion of an EVENT table that signals a data capture event with relationships to other tables, attributions, etc.

documentation:next_cdm:days_supply

Anonymous (anonymous@undisclosed.example.com) — 2017-07-06T19:18:46+0000

End of a drug exposure Proposals are now tracked as github issues link to issue in github * Requester: Klaus Bonadt, Christian Reich, Patrick Ryan * Discussion: here. ---------- Proposal Relevant table: FieldRequiredTypeDescriptiondrug_exposure_end_dateYesdateThe end date for the current instance of Drug utilization. Depending on different sources, it could be a known or an inferred date and denotes the last da…

documentation:next_cdm:deeper_semantic

Anonymous (anonymous@undisclosed.example.com) — 2017-06-13T16:03:02+0000

Proposing person: Vojtech Huser Title: Deeper semantic integration discussion: Use Case OMOP CDM via vocabulary axiom of one concept per entity enforces semantic standardization. Only one standard concept per entity. Yet in some instances, the vocabulary violates that axiom. (LOINC term for weight and SNOMED term for weight)

documentation:next_cdm:denominator_units

Anonymous (anonymous@undisclosed.example.com) — 2017-07-07T15:20:23+0000

Denominator Units for liquid drugs and quantity field in DRUG_EXPOSURE Proposals are now tracked as github issues link to github issue * Requester: Klaus Bonadt * Discussion: here. ---------- Proposal Proposal for conventions to achieve consistent entries in the attribute quantity of the DRUG_EXPOSURE table and entries in the DRUG_STRENGTH table. Eventually, we will be able to calculate the total amount of the active ingredient by

documentation:next_cdm:drg

Anonymous (anonymous@undisclosed.example.com) — 2017-07-06T14:39:21+0000

Proposals are now being stored as github issues: Link to issue in github

documentation:next_cdm:drug_benefit_indicator

Anonymous (anonymous@undisclosed.example.com) — 2017-01-09T14:40:26+0000

Drug Benefit Indicator * Requester: Don Torok * Discussion: Add the attribute to the payer plan period table to indicate if a person is likely to have prescription drug records for this period of time. Create a new payer plan period record when a person’s drug benefit status changes. Claims data often provides such an indicator, although it is not clear if the lack of drug benefits is because they are not included in a person's health insurance plan or if the plan does not report drug ben…

documentation:next_cdm:drug_classes

Anonymous (anonymous@undisclosed.example.com) — 2016-10-03T16:57:25+0000

Harmonization of Drug concepts Requester: Dmitry Dymshyts Proposal This proposal does not involve a change to the CDM schema. The idea is to make all ATC codes standard concepts. (change in OHDSI Vocabulary) Background EMR data contains concepts with Drug class information such as:

documentation:next_cdm:drug_dose

Anonymous (anonymous@undisclosed.example.com) — 2017-03-07T04:07:20+0000

Summary of Proposal * Add records for Ingredients and Drug forms containing standard units for each ingredient. * Define convention for quantity: Either as number of product unites, or as amount of ingredient. See below. * Remove effective_drug_dose.

documentation:next_cdm:drug_quantity

Anonymous (anonymous@undisclosed.example.com) — 2017-07-07T15:01:01+0000

Drug Quantity Proposals are now being tracked as github issues link to github issue * Requesters: Christian Reich, Klaus Bonadt ---------- Proposal We propose to abolish the effective_drug_dose field from the DRUG_EXPOSURE table entirely. The content can be handled by the quantity table.

documentation:next_cdm:drug_strength_for_quantified

Anonymous (anonymous@undisclosed.example.com) — 2017-07-06T14:40:19+0000

Expand Drug Strength tables to all Standard Concepts in the Drug Domain * Requester: Christian Reich * Discussion: Not yet * Proposals are now being stored as github issues: Link to issue ---------- Proposal Currently, only Clinical and Branded Drugs have a record in the DRUG_STRENGTH table. However, since all Standard Concepts are allowed to be used in the data and therefore dosing information is required for them, the algorithm should parse all Concept Classes:

documentation:next_cdm:encounter

Anonymous (anonymous@undisclosed.example.com) — 2016-06-08T12:50:31+0000

Add field or set of tables to deal with encounters within a visit * Requester: Daniella Meeker * Discussion: here. ---------- Proposal ---------- Use Cases

documentation:next_cdm:ensure_support_for_nqf-endorsed_ecqms

Anonymous (anonymous@undisclosed.example.com) — 2016-04-13T04:07:12+0000

Some of these items will be addressed with updates to items specific to data domains. I need help from collaborators to finish analysis of the gaps and alignment with the other changes. * Concept types associated with “Patient Refused Treatment”

documentation:next_cdm:eraroute

Anonymous (anonymous@undisclosed.example.com) — 2017-01-12T18:13:57+0000

Proposal by: Vojtech Huser Use Case: ingredients like neomycin can be taken oraly and localy (otic, ophtalmic). Such drug eras are medically distinct. Changes proposed: Modify DRUG_ERA table () and add route_concept_id column (as an optional column)

documentation:next_cdm:lat_long

Anonymous (anonymous@undisclosed.example.com) — 2017-08-02T13:46:50+0000

Add Latitude and Longitude to Location Table Proposals are now housed on github link to github issue * Proposal Owner: Gowtham Rao * Use cases: For standardized geospatial visualization and analysis * Related proposals: * Discussion: * Background: For standardized geospatial visualization and analysis, addre…

documentation:next_cdm:location_history

Anonymous (anonymous@undisclosed.example.com) — 2016-10-14T18:15:53+0000

Location History * Requester: Robert Miller * Discussion: here. ---------- Proposal The location_id in the Person table is only capable of storing a single location address for an individual. We want to know where a person's location was for a given date-time. This maybe solved using a location_history table, which acts as a relational entity between Person and Location.

documentation:next_cdm:metadata

Anonymous (anonymous@undisclosed.example.com) — 2017-07-10T16:26:21+0000

Metadata Proposals are now tracked as github issues link to github issue Proposing person: Vojtech Huser Discussion link: Table CDM_SOURCE provides metadata. () Use case * display metadata within Atlas-Achilles Web (when reviewing data characterization plots and tables)

documentation:next_cdm:multi_level_linkage

Anonymous (anonymous@undisclosed.example.com) — 2017-03-01T17:06:17+0000

Food Component Table * Proposer: Clair Blacketer Proposal Add an optional table similar to the DRUG_STRENGTH table that would contain information about foods such as calories, fat, and sugar content. The specific use case I am thinking of is related to the

documentation:next_cdm:nlp

Anonymous (anonymous@undisclosed.example.com) — 2017-07-13T19:17:43+0000

New Fields to NOTE table, new NLP table Proposals are now being tracked as github issues github issue * Requester: Noemie Elhadad, Hua Xu * Forum Discussion: here. ---------- Proposal Final Version Previous Version

documentation:next_cdm:package_size

Anonymous (anonymous@undisclosed.example.com) — 2017-07-07T16:39:17+0000

Add Package or Box size and Supplier to Drugs Proposals are now being tracked as github issues link to github issue * Requester: Christian Reich * Discussion: In WG ---------- Proposal In many other countries, drugs are not dispensed in the pharmacies, with small exceptions (usually ointments that have to be created fresh). Instead, all prescription drugs are packaged just like OTC drugs in the US, with the number of content usually lasting for one, two or three months. These products …

documentation:next_cdm:place_of_service_source_concept_id

Anonymous (anonymous@undisclosed.example.com) — 2017-03-14T17:49:53+0000

Add place_of_service_concept_id to care_site table Proposal: This is a small proposal to add place_of_service_source_concept_id. It is a general OMOP convention to represent X_source_value as X_source_concept_id and X_concept_id, where X_concept_id is always standard-vocabulary for the domain, and X_source_concept_id maybe standard/non-standard vocabulary that is an integer representation of X_source_value. We don't have X_source_concept_id in care_site and this proposal is to add it.

documentation:next_cdm:procedure_codes

Anonymous (anonymous@undisclosed.example.com) — 2015-11-04T18:27:45+0000

Harmonization of procedure concepts * Requester: Vojtech Huser * Discussion: ---- Proposal This proposal does not involve a change to the CDM schema. This is follow up on discussion at Bethesda F2F meeting. It was suggested to do an evaluation of granularity in various procedural terminologies.

documentation:next_cdm:procedure_occurrence_modifier

Anonymous (anonymous@undisclosed.example.com) — 2017-08-02T14:47:36+0000

Procedure Occurrence Modifier Proposals are now housed as github issues link to github issue * Requester: Evanette Burrows * Discussion: here. ---------- Proposal FieldRequiredTypeDescriptionfieldYesintegerdescription ---------- Use Cases

documentation:next_cdm:realm

Anonymous (anonymous@undisclosed.example.com) — 2017-08-02T13:46:38+0000

Proposals are now housed on github link to github issue Requestor: Vojtech Huser Discussion: Current CDM version may contain some concepts that are specific to a region. For example, some constructs reflect USA centric concepts. * We should somehow mark those region-specific columns (in various tables)

documentation:next_cdm:referrals

Anonymous (anonymous@undisclosed.example.com) — 2017-01-10T21:14:48+0000

Encounters, Care Transitions and Referral Information * Requestor: Daniella Meeker Add field or set of tables to deal with encounters within a visit Preconditions require better definitions on the distinctions between EVENTS, VISITS, ENCOUNTERS, AND EPISODES OF CARE.

documentation:next_cdm:schema_revisions

Anonymous (anonymous@undisclosed.example.com) — 2018-02-12T20:23:32+0000

CDM Schema Revisions (needs rewriting to accommodate schemas in the specs) * Requesters: Frank DeFalco, Patrick Ryan ---------- Proposal We propose changes to the tables included in the CDM schema in order to clarify their intent. Specifically we propose

documentation:next_cdm:single_cost

Anonymous (anonymous@undisclosed.example.com) — 2016-03-08T19:09:08+0000

Single Cost Table * Requester: Duryea family, Outcomes Insights, Inc. * Discussion: here and here. ---------- Proposal Proposal to consolidate all current cost tables (Procedure_Cost, Drug_Cost, Device_Cost, Visit_Cost) in V5.0 into one single table. The table could be connected to any of the Domain tables (Procedure_Occurrence, Condition_Occurrence, Drug_Exposure, Device_Exposure, Observation, Measurement).

documentation:next_cdm:smq

Anonymous (anonymous@undisclosed.example.com) — 2016-06-08T12:49:25+0000

Create SMQ as a Classification system with correct relationships to MedDRA * Requester: Don O'Hara * Discussion: here. ---------- Proposal ---------- Use Cases

documentation:next_cdm:snomed

Anonymous (anonymous@undisclosed.example.com) — 2017-04-04T13:02:26+0000

Greetings I am requesting that Athena/Usagi split the SNOMED CT load into individual Country specific editions. Meaning that when downloading SNOMED CT content from Athena or importing SNOMED CT into Usagi, the user would have the option to import:

documentation:next_cdm:time

Anonymous (anonymous@undisclosed.example.com) — 2017-07-06T15:05:33+0000

Add Time Field to various Occurrence and Exposure Tables Proposals are now being stored as github issues link to issue in github While v5 visit_occurrence table supports both date and time of event, other occurrence tables and exposure tables such as drug, condition, and procedure support only the date level. It is desirable to have the option to include specific time data for such occurrences. Our goal is to allow temporal operations finer than day without disrupting OHDSI by requiring majo…

documentation:next_cdm:tobacco

Anonymous (anonymous@undisclosed.example.com) — 2016-05-26T17:54:56+0000

Proposal draft: [Discussion] Related Documents [NQF Measures: Tobacco Use: Screening & Cessation Intervention] [NQF Tobacco Use and Sessation Vocabulary] Meaningful Use Core Measures: Smoking Status

documentation:next_cdm:transitionofcare

Anonymous (anonymous@undisclosed.example.com) — 2017-07-13T17:14:25+0000

Proposals are now being tracked as github issues github issue [Handling of admission-discharge transfers (ADT) to CDM] Discussion Some considerations: * This could be an attribute of VISIT (if VISIT becomes synonymous to ENCOUNTER) or * ENCOUNTER (or DATA CAPTURE EVENT) could become a new, optional staging table with optional TRANSFER FROM ENCOUNTER and TRANSFER TO ENCOUNTER and VISIT could be a derived table with standard rules.

documentation:next_cdm:visit_concepts

Anonymous (anonymous@undisclosed.example.com) — 2017-03-17T12:34:14+0000

Discussion

documentation:next_cdm:visits_microvisits

Anonymous (anonymous@undisclosed.example.com) — 2017-07-06T16:30:00+0000

Proposal for Visit_detail: Represent granular encounters or microvisits Proposals are now housed as github issues link to github issue Proposal Owner: Gowtham Rao Use cases: Also addresses using new Definition…

documentation:next_cdm:visualization

Anonymous (anonymous@undisclosed.example.com) — 2017-01-31T15:14:49+0000

Vocabulary/Population Visualization Working Group Work on this has moved to its own working group for now: