Git Product home page Git Product logo

projectehr's People

Contributors

avaidyam avatar aw449 avatar john-squire avatar kkyl avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

projectehr's Issues

Build local FHIR store for testing

See required resources here.

Also see FHIR documentation here.

Of note, FHIR stores clinical notes in a non-standard way, using DocumentReference with an attached Binary that actually contains the note contents (HTML, etc.). Here is an example.

Do note the format of the reference element:

  • If it refers to an external reference on the same server, then it can be a relative reference like medication/@12345
  • If it refers to an external reference on a different server, then you need the full url – eg http://fhir.myserver/medication/@12345
  • In either of the above examples you can have the full history – eg medication/@12345/history/@3 – to refer to a specific version of the resource
  • If it is a reference to a contained resource, then use the # symbol – eg #12345 – where the id is the id on the contained element, and doesn’t include the resource type

SimHospital functionality

Currently, every case has to be fully manually defined by the user, which can be time consuming. Instead, we may want to simulate patient data (i.e. individual lab results such as for a CMP, given mean/std to use for randomization), the whole patient profile (i.e. given a patient ‘archetype’), or multiple patients all at once. See SimHospital for an example. Also see Synthea.


Example using Gout:
image

Initial Project Backlog

Goals:

  • wants to throw everything into this tool and centralize things
  • sim purposes: pt chart in the background while running a sim
  • enter in admission orders, document visit/encounter, etc as part of phase 2 OSCEs
  • "living breathing EMR with different data accessibility"
  • for simulation, avoid PPT and be able to handle minute-by-minute
  • UI like EPIC
  • view lab/imaging results
  • active orders list (order rx/procedure OR use order sets)
  • write a basic note, EPIC sidebar activities
  • insurance info + Rx cost
  • reusing cases (idea: profiles with STAGES (i.e. Hanson_1, Hanson_2, etc) with automated progression between stages which are deltas)

major UI components:

  1. patient schedule page
  2. patient chart page layout (sidebar, tabs on top, different sub-pages)
  3. patient sidebar (pt info, personal notes, hover popups with detail, etc)
  4. chart review (filter by note/lab/enc/etc)
  5. note viewer (essentially sandboxed HTML content)
  6. note composer (essentially a WYSIWYG editor → HTML)
  7. flowsheets/results review (grid of all lab results chronologically)
  8. add orders (popup list with an HTML form for each type of order; labs, referrals, Rx, etc)
  9. rooming page (vitals entry, etc)
  10. wrap-up page (follow-up, patient edu, etc)
  11. history page (PMHx, PSHx, FHx, SHx, etc)
  12. visit page (visit diagnoses, etc)
  13. NoteWriter (interactive smartblocks for HPI, ROS, PE - try .physicalexam in your clinic notes if you haven't already!)

review the following standards:

  1. ICD-10 codes for diagnoses (specifically sub-coding and specifiers, etc)
  2. LOINC codes for lab orders (imaging or pathology, etc)
  3. RxNorm codes for all possible FDA approved Rx (incl every dosage and dosage form, etc)
  4. FHIR documents and an [example bundle of what we're working with] (https://healthintellect.github.io/fhir-ui/examples/fhir-examples/patient-bundle)

Sid: patient chart page + patient sidebar + rooming page
Tony: integrating LOINC codes + RxNorm codes for the order builder
Anthony: base app + page navigation (i.e. schedule -> patient tab, inner pages knowing which MRN is loaded currently, etc)
JD: note viewer + note composer + notewriter
Kristy: patient schedule table
@avaidyam: flowsheets/results review

Seeded sample data

We need to incorporate sample data for testing and development of the EHR. See R4 generated sample data. The dates of certain encounters will need to be shifted dynamically at runtime to preserve the patient’s storyboard/timeline (i.e. age 60 for encounter A, age 70 for encounter B).

Patient Home → Orders Composer

  • Add Order Button (Left)
  • Pending Orders List (Right)
  • Individual Order Composer (Dialog)

Order Composer

IMG_0196

Order Type

Order Type Used when…
House Icon Lab tests are ordered in the ambulatory setting
Bed Icon Lab tests are ordered in the inpatient setting

Status Field

Status Used when…
Normal Do not use because this will cause the orders to automatically be released to the lab as if the patient has arrived at the lab and had their tests drawn. Providers and staff should only use standing or future.
Standing For repeat labs such as AMS INR’s. You want multiple orders to be done in the future. When setting up a Standing Order, it is important that you include in the Interval field how often the test should be drawn as well as indicate in the Count field the number of times the lab should be drawn.
Future Should be used for all lab orders that are not Standing (repeat orders). Patient will show up later for this lab order. (Example Fasting Glucose or Lipid Panel)

Date Fields

Date Fields Used when…
Expected Date Provider indicates the date patient can have the lab drawn. Note: labs can be drawn up to 7 days before the expected date. For example – you would like to order a TSH to be drawn in 3 months after you have made changes to a patient’s thyroid medicine. You should indicate that the Expected Date should be 3 months from today’s date. If you left the default Expected Date to today, the patient could have the TSH drawn any time from today forward. The Lab Department will draw the test based on the Expected Date.
Expires Date Provider indicates the last date a patient can have a lab drawn. Note: labs can draw up to 7 days past the expiration date.

Priority Field

Priority Used when…
Routine Routine is the most common priority and should not be used for urgent or emergent situations.
STAT Results will be available within an hour in the ambulatory setting once the specimen arrives in the laboratory.
Timed Not used in the out-patient setting.
Urgent Results will be available within 2 hours once the specimen arrives in the laboratory.

Class Field

Class Used when…
Lab Collect Test will be resulted by Organization’s Laboratory. Example: CMP and CBC lab will be collected, tested, and resulted at Organization. Example: Pro-time will be collected by Home Care. The specimen will be delivered to the Carle laboratory where it will be tested and resulted.
Clinic Collect Patient specimen is collected in the provider office during patient visit. Example: Throat swab collected in the doctor’s office.
External Collect Patient will have an ordered test collected, tested, and resulted outside of the organization. Example: Patient needs CBC and CMP drawn at Hospital.

Pending Order List

IMG_0197

TBD


Order Search

IMG_0209

TBD

Schedule UI

Screenshot 2023-10-05 at 10 47 50 AM Screenshot 2023-10-05 at 10 48 05 AM

Table Columns:

Name Description
Bar Color displays patient rooming status.
Circle Color displayed depends on organization/department needs.
Status Current rooming status and exam room number.
Bar Color displays patient rooming status.
Patient Patient name and age.
Provider Provider name.
Type Visit type (office visit, well child visit, physical exam, etc.).
Notes Appointment notes/details incl. chief complaint.
  • Clicking on the row should bring up the preview on the right side.
  • Double-clicking on the row should open a new patient tab.
  • Toolbar on top should have several options (currently undefined for our needs).
  • Table toolbar should have a schedule name button and editable date button.
  • Clicking the schedule name should bring a dropdown menu to select a schedule across departments AND filter by provider name.

Patient Home → Rooming/Plan/WrapUp Tabs

The Rooming Tab contains:

  • Reason for Visit → edits the chief complaint for the current encounter (office visit or admission)
  • Vital Signs → simple UI to edit the underlying VS flowsheet
  • History, Birth Control Hx, Immunizations → with links to separate Tab
  • Medications → with link to separate Tab
  • Episodes, Flu Vaccine Screen, BestPractice, Questionnaires, Outside Meds, Verify Benefits, Pt ClinRev, Additional Vitals → Unrelated to our scope of work

The Plan Tab contains:

  • Problem List → with link to separate Tab
  • Medication Management → with link to separate Tab
  • Pt Clin Review, Chronic Care Mgmt, Goals, BestPractice → Unrelated to our scope of work

The Wrap-Up Tab contains:

  • Patient Instructions →
  • Follow-up Instructions →
  • ClinRef, Charge Capture, MU (Meaningful Use) Status → Unrelated to our scope of work.

image
image
image

Modern UI Option

Right now we’re trying to emulate existing EHRs for training purposes, but in the future it may be helpful actually restructure how the data/UI is viewed and interacted with.

IMG_0221
IMG_0230
IMG_0229
IMG_0228
IMG_0227
IMG_0226
IMG_0225
IMG_0224
IMG_0223
IMG_0222
(Examples from Google’s Care Studio.)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.