| Other Duties as Assigned: |
My primary responsibility has been Epic Interface testing but I often lend a hand in other areas. I have performed build/testing tasks wherever needed - this includes building documentation texts with SmartTools and updating Master Files.
Tasks I have performed in the Ambulatory setting:
At Dean Clinic (in addition to interface testing)
- Assisted with Documentation tools especially order sets
- Updated preference lists
- Helped with : facility/service area/ location/ dept
- Helped clean up patient IDs using Identity
- Ran report generator reports (find all deceased patients, and other searches)
- Fixed procedure synonyms and others due to import spreadsheet errors
- Entered interface map codes into the procedure database
- Updated Epic procedure names to match lab's
- Updated reason for cancel to synch up with lab's
- Created appointments in Cadence for testing
- Helped verify billing
- Inactivated procedure codes
- Helped resolve Provider and Department build issues
- Prepared and submitted Specimen source category list for importing
- Updated procedure import and resubmitted.
In general orchestrated the build items that need to be there for the interface
- Prepared Print group specification for programming
- Documented what will be needed for department to maintain procedure master file
- Worked on the documentation for the clinical group, help desk, and Dean lab.
At Monroe Clinic (in addition to interface work)
- Updated Provider security records
- Prepared securty import spreadsheet for new providers
- Assisted with workflow documentation
- Added provider records for radiology rooms
- Added locations to 3 work queues
- Reformatted radiology letter
- Assisted with print testing
- Changed procedure codes to orderable
- Marked inventory supplies as chargeable
- Added order questions to procedures
- Assisted with procedure set up for supplies
- Added chart locations
- Added synonyms to procedure records
At Allina
- Met with department representatives to document hospital and ambulatory workflows and used to develop integrated testing scenarios.
- Helped the training department create test patients for testing integrated testing scenarios
At ThedaCare (in addition to interface testing)
- Family Practice, Ortho, Urology SmartTool development:
I was given texts in Word and I used them as a basis to build Epic clinical documentation components
- Updated Reason For Visit master file
- Health maintenance set up
(I used to teach the HM classes when I worked for Epic)
- Updated Dx names
- Associated order questions with procedure codes (procedure master file)
- Updated Diagnosis and Procedure synonyms
- Updated specimen sources
- Assisted with developing procedures for abstracting medical data into Epic
At Sutter
- On a team that designed, created, and tested order transmittal
(I used to teach the order transmittal class at Epic)
- Defined and document clinic workflows from existing workflows
- Updated workstations, providers, order transmittals
- Created report generator reports of printer, workstation, order trans set up
- Created standards for SmartText names and implemented name changes
- SmartText/SmartLink testing
- deactivated allergens
- cleaned up category lists
- updated visit types
- updated list of emergency relation contact
- worked on preference lists for 3 go-live departments
At Exempla:
- Assisted with upgrade for Y2K - they were behind several versions so it was basically a re-install.
I was on a team that analyzed each master file and what needed to be done for conversion to Y2K upgrade then tested the new system. This involved every master file in Epic ambulatory EMR and Scheduling.
- Prepared import spreadsheets.
Inpatient Order Products Specialist for St. Mary's Hospital
- Designed Lab workflows between Epic Medical Record and HBOC's Star Lab
- Worked with hospital specialty departments to configure orders, preference lists, charge navigator, and general orders workflow including use of system lists
- Attended all dbv sessions and worked in a 4 person team on system build for orders.
- Chaired meetings to review and provide feedback on collaboratively built ordersets.
|