User Tools

Site Tools


start

iTrust: Role-Based Healthcare

Welcome to the iTrust wiki!! iTrust was founded as a class project for Software Engineering at North Carolina State University, and is now maintained by the Realsearch Research Group. iTrust was aimed to teach various testing methods and automatic testing techniques in the curriculum of the course. iTrust is a medical application that provides patients with a means to keep up with their medical history and records as well as communicate with their doctors, including selecting which doctors to be their primary caregiver, seeing and sharing satisfaction results, and other tasks. iTrust is also an interface for medical staff from various locations. iTrust allows the staff to keep track of their patients through messaging capabilities, scheduling of office visits, diagnoses, prescribing medication, ordering and viewing lab results, among other funtions. Privacy and security of patient records are ensured, as protected by the HIPAA statute.

Demo: v21.0

Try iTrust for yourself! This demo is for iTrust v21.0, built from requirements v27.0. The roadmap explains the versions.

Also, there is an image titled “iTrust 12.0” that you can check out from NC State's VCL if you belong to the EHR User's group.

Source Code: v21.0

iTrust is open source!

NC State Students can download v21.0 as a starting point for developing v21 during the Spring 2016 semester from https://github.ncsu.edu/engr-csc326-staff/iTrust-v21 [NCSU Login Required]

The Spring 2015 version is still available on SourceForge.

Visit our project page on SourceForge.

Deployment

After you have the source, learn how to deploy it:

Requirements: v27

The most current version of the requirements can be found at the requirements page.

Other artifacts: v21.0

  • The How do I...? page contains straightforward answers to common things you may want to do when developing.
  • The design notes page contains some explanations of the archetypal classes in the design.

For Administrators and TAs

  • Between semesters, iTrust also goes through housekeeping.
  • The developing requirements page is a password-protected section where new ideas, requirements, and other artifacts are developed by instructors and stakeholders.
  • Information on how to administer the demo deployment of iTrust and more are also password-protected.
  • Administrators may also want to deploy an instance of iTrust to a Linux server.

Copyright ©2004-2015. North Carolina State University, Dr. Laurie Williams, Andy Meneely, Sarah Heckman, Lauren Hayward, Ben Smith, Jason King


se-realsearch-bar-2.jpg

start.txt · Last modified: 2016/08/23 07:59 by seelder