Project Overview > Project Specifications | Wireframe Examples
Title: LindseyJones University
Project Specifications
Access
LindseyJones, by agreement, will allow colleges and university to have access to these clinical simulation exercises. Universities will purchase the rights to “sign up” a certain number of students (licenses).
Colleges and universities will be given access codes that will allow their students to create their own username and password. Both the student’s and the college’s access is controlled by an expiration date and a predetermined number of licenses. On-line payment processing will NOT be required in this project as students are not payers.
Example: A university purchases 20 “spots” or licenses for one year. The University is signed up by LindseyJones Admin. Notification is sent to the university to finish setting up their own admin (coorindator) accounts (passwords, preference, etc).
The Univ coordinator will initialize a student account by providing name and email address of the person they wish to add. A notification email is sent to that person with a secure link. When the student clicks on the link they are immediately taken to a place to finish setting up their account, including password, alt email, etc. Then to finish setting up, a confirmation email is sent to the student, when they click the confirming link, they are finalized and they are, for the first time taken to their dashboard.
Coorindators at the Universities should be able to control a students expiration date, the clinical simulations that are available to them, and if teaching mode is persmissable or not.
Email Collection
LindseyJones is interested in collecting all email addresses for other marketing and future purposes. All emails, including university contacts and individual students, should be recorded in a database. This data persists, in spite of removal of students from the records. For this purpose, we want all usernames to be valid email addresses. The record should record the email address and the date of add. To ensure the emails are current, valid email addresses, we would love for new users to have to confirm their email addresses by having to click a link in a confirming email sent to them upon registration. We’re open to suggestions here.
Demo Accounts
For marketing purposes, LindseyJones would like to be able to extend temporary license to Universities, AND limit their access to specific Clinical Simulation exercises of our choosing, as well as obviously customizing their start date and expiration date.
Clinical Simulation Editing
We need some basic abilities to quickly change and edit data as well as add new content.
We want to be able to edit individual fields in the CONTENT database.
Each Clinical Simulation exercise will be held in a different table in the CONTENT database.
Want to be able to add an entire clin sim exercise (add a table).
Clinical Simulation Exercises and Scoring
The student will be able to log on, choose one of about 30 simulation titles, and complete the exercise, and then receive scores. The user will be given the option to perform the exercise in TEACHING or TESTING mode. In teaching mode, additional rationale data is provided live with each choice. It will take approx 10-20 minutes to complete one exercise and the student will navigate screen-to-screen through approximately 8-12 option screens. Each screen has options of tests or actions they can choose to do to a fictional patient. The user achieves scores for each option they select. Values range from –3 to +3 points and a final score screen is shown.
All patient data is static data in a database. So records include fields: Test item, test result, value, rationale, and few other fields that denote category, type of situation, and control features fields for navigation purposes. Once the exercise is complete, the student needs to be able to navigate through the exercise again, viewing what they picked and viewing rationale for each option. We’re not sure exactly how we are going to handle this yet. Although the real exam is time-limited, these exercises will track and report time, but will not be limited (automatic exit) by time.
View a current On-line Example
1 Visit HYPERLINK "http://www.NBRC.org" www.NBRC.org
2 Click on the Examinations square
3 Select “Registered Respiratory Therapist (RRT)”
4 Click on “Free CSE Practice Examination” in the Links box on the right
5 Type your name (or any text) in the name field and click Login (its not a true login)
6 Click Begin.
This is a free test by the actual testing authority. LindseyJones will copy the exact environment very closely. Simply type in any text in the name field or an email address if you want to see results and hit log in. Then click begin. It is free to anyone.
Student Access Expiration Dates
Normally, the university has a single expiration date. However, LindseyJones wants the ability to extend permission to an individual person directly, not associated with any institution. This helps us with some legacy customers are our MAC dependent or having technical issues we cannot solve. In such a case, we want the ability to set individual expiration dates. We could, depending on the opinion of the developer, make all students have an expiration date, including those signed up under a university. By default that expiration date would match the school’s expiration date. But perhaps the university instructors/coordinators want to grant time-limited access to whomever they choose.
Reports
All reports should be viewable on the screen with an option to print
Students
Should be able to print a report after each exercise of their scores. The following will be on the report
Name
Date
Time began simulation
Time consumed in the simulation
Pass / Fail
Achieved Information Gather (IG) score – raw number
Achieved Decision Making (DM) score – raw number
Max IG (max points possible)
Max DM (max points possible)
Min IG (minimum needed for passing)
Min DM (minimum needed for passing
Achieved IG%
Achieved DM%
Omission %
Commission %
Instructor/Coordinators
Selected by date range:
List of Student and their results
Organized by student alphabetically
Organized by Date (newest to oldest)
Organized by Exercise (then by name alphabetically)
LindseyJones Admin
Lists of clients (expired and current)
Feedback Log
Record Keeping
Each time a student begins a clinical simulation test, their attempt must be logged into a database. If they finish, a few pieces of score data must be recorded When the student logs into the system, their selection screen should show which exercises they have done. They may repeat exercises, but they need to be able to see which ones they have done.
Categorization
Clinical simulation exercises will be categorized into 4-8 categories
We provide all data. Currently housed in MS Access databases, we can translate all data into mySQL databases. We will simply create the databases according to the developers requirements, including structure, etc. Our vision is that all clinical simulation content will be housed in one CONTENT database with table housing each exercise. MEMBERSHIP INFO In another database, SESSION information in another. We we are flexible.
Databases and Structure
Although this is flexible to the recommendations of the developer, we vision:
A CONTENT Database – where Clinical simulation data is held. Each separate clinical simulation will be held in its own table.
LindseyJones can supply the database in MS access, which the developer can convert to mySQL.
A SESSION database – where individual information is held.
Possible a separate EMAIL database – see section on Email Collection
User Feedback
In all simulation screens, we want the end-user to be able to give feedback on the content there are dealing with. Their feedback is placed in a log. Each entry should contain their free-text feedback and the simulation exercise and menu they are in (context). We will inspect and print these logs for quality improvement purposes. This is not a place for students to ASK questions. We are not intending on providing instruction to individual students or responding to them in this way. If instructor’s have questions we will deal with them through email
Language and Annotation
LindseyJones will be needing to maintain these exercises in-house. Minor code changes may be made by our staff, who have some web-based programming experienced. Thus, we prefer the primary language to be php and mySQL. But we are open to other tools such as the use of apache, ruby on rails. etc. Code will be examined to ensure adequate annotation. We like code to follow proper formatting conventions.
Workspace
We will operate under the web hosting provider, Bluehost. We will need to know up front what server-sided tools needed so we can ensure our hosting services are adequate. We know they obviously support php, mysql, ruby on rails, and quite a few others..
Disclaimer
Developer will be required to sign a non-disclosure agreement.
Design and Layout
LindseyJones can be the primary designer of the look and feel of the testing center. BUT we would rather work with professional designers provided by the developer, especially since that relationships is so intertwined. Although we dislike the clinical simulation environment, the exercise format and layout is dictated by the actual testing environment and our claim to fame is that we provide students with a similar look and feel to the actual test. All graphics, illustrations will be provided to the developer.
Payment for Services
LindseyJones prefers to pay by retainer and then subsequent milestone achievements. We like 3 payments, retainer, middle milestone, and finish. We like 30% - 40% - 30%. But flexible.
Scope Creep
We try to keep it at a minimum, but we know it will happen. We like a little scope creep built into the price. Otherwise we will simply ask for interim revised quotes if we decide to change the project appreciably. Initial proposals should include some was to costing out scope creep after the begining of a project that goes beyond the quoted scope. (ie, a cost per hour, etc).
Email Capture
All user names should be email address. We will need to capture all emails (instructors and students) in a database, never to be deleted, even if clients are removed or expired. Obviously email address are gold to us.
Function Description:
LindseyJones Admin should be able to:
Initialize a university
Poviding the university name, alt contacts and emails, start date and end date of service, demo or full account
if Demo Account - LindseyJones should be able specify (by check box) which exercises will be available.
Edit any fields, including name, start and end dates
Send an automatic email with forwardable links to Universities
Print reports on
Client list, about to expire, peak usage times, sessions by univeristy, date, IP addresses.
University Admin (Coordinator) should be able to
Forward an invitation link to any students
View and print entire list of current students (who are using the system under their license)
Delete students
Modify students' contact information, which exercises are available (per student would be great, but at least globally)
Resend invitation links
Reports
Obtain usage information with graphics and the ability to drill down on who is using the system and who is not. (used for determine if deletion is important or not)