Giter Club home page Giter Club logo

non-clinical-rounding's Introduction

Non Clinical Rounding

Features

  • Rounding List (full Rounding List, rooms with alerts, rooms with low sentiment)
  • Clickable rounding map with sentiment and alert notifications
  • Interactive survey for selected room
  • View survey history
  • Cross-platform, responsive application

Dependencies

  • Dataverse with Healthcare data model
    • Patient (Contact)
    • Location
    • Encounter

Deployment

  1. Deploy managed solution to a Dataverse environment
    1. Publish the Non-Clinical Rounding and Rounding History Power Apps
  2. Assign Non Clinical Rounding Administration security role
  3. Deploy sample data (or create your own)
  4. Share app with users and assign security roles

Major components

  • Model Driven Power App: Non-Clinical Rounding
  • Table: Rounding Detail
  • Table: Rounding Session
  • Security Role: Non Clinical Rounding User
  • Security Role: Non Clinical Rounding Administration

Design Decisions

  • Use of FHIR concept of Encounter to track experience across multiple locations

  • Use of FHIR concept of Encounter Locations to list and filter based on a status of Active

    • https://www.hl7.org/fhir/encounter-definitions.html#Encounter.location
    • This is used to show the list of beds (Locations), and allow the traversing of related information
    • A configured Rounding Detail table includes direct links to the the Patient and Location, based on the Encounter details. Allows for use of Power Platform & Dataverse features for workflow and reporting, without modification to the FHIR data.
  • Note: Sample room map uses Power Apps experimental feature to select and open room record

Sample Data

This repository includes sample data that allows testing/modification without requiring a live FHIR integration.

  1. Import the RoundingDetail.csv file found in the solutions folder of this repository

    1. Not sure how? Navigate to Power Apps Maker Portal->Data->Rounding Detail->Data then use the Import from Excel action
    2. Update the data map to relate the Title column from the .csv to the Title column in Dataverse
  2. Optional: Update references for each Rounding Detail record to a related Patient, Encounter, and Location. Doing so will enable additional views/reporting summarized for an Encounter (regardless of Location), summarized for a Location (regardless of Patient), etc.

If you choose to create your own sample data, the Rounding Map (canvas Page) will need to be updated to reflect the room names/numbers/map location in order to behave as expected.

Solution History

NonClinicalRounding 1.0.5

Addressed bug for the Non-Clinical Rounding User security role to create Rounding Sessions.

NonClinicalRounding 1.0.4

Re-added form-embedded canvas Power App.

NonClinicalRounding 1.0.3

Addressed some visual defects.

  • Canvas components - adjusting width for better mobile phone experience
  • Rounding Detail form - Added Encounter and Patient lookup fields to Details tab for reference (read-only)

NonClinicalRounding 1.0.2

First deployable package.

  • Added user security role

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

non-clinical-rounding's People

Contributors

mathyousee avatar microsoft-github-operations[bot] avatar microsoftopensource avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

non-clinical-rounding's Issues

Add sample code to dynamically generate Rounding Details

The repository has a sample data file, which is good for standing up a lightweight test, but organizations will want to use their own familiar building names, locations, etc.

Recommend a cloud flow in a separate solution, which could be layered on the non-clinical-rounding solution in order to create/deactivate rounding details records.

Add more details for deployment / design considerations

Since this takes advantage of a low code configuration platform, some additional documentation for both citizen developers and pro developers would benefit people or organizations who use this sample code.

Things like the details for options of where some of the foundational data can be sourced from for various deployment scenarios (e.g. what if a customer has FHIR bundles vs data in a data warehouse, how does this support varying starting points for deployment, etc.)

Support data routes for FHIR entities

There is a preview feature in Dataverse which uses the concept of a virtual data route for certain FHIR resources. The metadata definitions and sample app could be updated to leverage this virtual data route.

This update would enhance the app so that either persisted data, or virtual data, would be supported without changes to the app, so there is definite benefit despite the refactoring required to change the existing relationships and app behavior.

Would also be worth keeping a branch that doesn't include virtual data routes.

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.