Skip to content

Family History Mapping OSCAR to E2E

Jeremy Ho edited this page Apr 25, 2013 · 3 revisions

E2E Mapping Family History Section

The E2E Family History section contains data pertaining to the conditions that the patient's family members have or have had in the past that may affect the patient's treatment.

General Assumptions

User Assumptions

  • The provider shall enter all family history entries into OSCAR under the Family History section of the Encounter page
  • All relevant fields presented will be filled with data if applicable

Data Assumptions

  • We expect family history data to be a freetext field which will make sense to a human reader
  • Family History data will not be entered in other parts of OSCAR

Issues

Issue 1

  • OSCAR records relationship as freetext while E2E expects codified data

Options

  • Create a freetext parser to map freetext data to codes
  • Ignore the code and default to other and saving the relationship freetext as a field

Decision

  • We decided to default the code to other for the interim because parsing freetext to a code may cause more harm than good
  • Freetext parsing is inherently not safe - you may be able to translate most cases without issue, but there will exist edge cases that can cause data loss
  • Flag this to OSCAR and GPI to discuss

Mapping

Relevant OSCAR DB Tables: casemgmt_note, casemgmt_note_ext

Family History Mapping Table

Current Iteration: 13

General Topics

Resources


Previous Iteration: 12

Previous Iteration: 11

Previous Iteration: 10

Previous Iteration: 9

Previous Iteration: 8

Previous Iteration: 7

Previous Iteration: 6

Previous Iteration: 5

Previous Iteration: 4

Previous Iteration: 3

Previous Iteration: 2

Previous Iteration: 1

Previous Iteration: 0

Clone this wiki locally