Skip to content

Encounter Mapping OSCAR to E2E

Jeremy Ho edited this page Dec 16, 2013 · 2 revisions

E2E Mapping Encounter Section

The E2E Encounter section contains data pertaining to the patient's visits or encounters with the provider or care practicioner. This data includes notes and annotations that the doctor would have saved regarding the visit.

General Assumptions

User Assumptions

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

Data Assumptions

  • We expect encounter data to be a freetext field which will make sense to a human reader
  • Encounter data will not be entered in other parts of OSCAR

Issues

Issue 1

  • OSCAR records encounters as freetext while E2E expects codified data

Options

  • Create a freetext parser to map freetext data to codes
  • Ignore the code and populate with freetext, adding codes if available

Decision

  • We decided to ignore the code requirement and populate the section with freetext on a best-effort basis
  • If a code exists within the entry, it will be included
  • Flag this to OSCAR and GPI to discuss

Mapping

Relevant OSCAR DB Tables: casemgmt_note

Encounter 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