id stringlengths 4 44 | content stringlengths 36 264k | summary stringclasses 2
values | layer stringclasses 3
values |
|---|---|---|---|
UC10E1 | The health care professional types an invalid medical identification number and is prompted to try again.
| Use Cases | |
UC10E2 | The patient chosen is not the desired patient. The health care professional does not confirm the selection and is prompted to try again.
| Use Cases | |
UC10S1 | The health care personnel enters a MID [E1] of a patient and confirms their selection [E2]. The health care personnel may enter/edit personal health information including editing historical values from Data Format 6.4.1, 6.4.2, 6.4.3, and 6.4.4, immunizations, and office visit information (date, diagnoses, medication, ... | Use Cases | |
UC10S2 | For the patient, the HCP can choose either height or weight to graph. The HCP is presented with a line chart giving the chosen measurements (either height or weight) of the patient spanning the last 3 calendar years of data, averaged by quarters (January-March, April-June, July-September, October-December) [E3].
| Use Cases | |
UC11E1 | The HCP types an invalid medical identification number and is prompted to try again.
| Use Cases | |
UC11E2 | The patient chosen is not the desired patient. The health care personnel does not confirm the selection and is prompted to try again.
| Use Cases | |
UC11S1 | The HCP enters a MID [E1] or name of a patient and confirms their selection [E2]. The HCP documents the office visit date; hospital location of the office visit, if any, (the default should be the HCP's home location); and notes (numbers, characters, #, ;, ?, -, ', ., :, blankspace and carriage return are all allowed i... | Use Cases | |
UC11S2 | HCPs can return to an office visit and modify or delete the fields of the office visit [date, hospital, notes, prescriptions, laboratory procedures (UC26), referral (UC33), diagnoses, procedures, and/or immunizations]. The event is logged (UC 5, S8) and the HCP is returned in the specific office visit record to verify ... | Use Cases | |
UC12 | The software tester authenticates himself or herself in the iTrust Medical Records system (UC2). He or she is then presented with the actual operational profile of the operations of the iTrust Medical Records where the use percentage is the % of total transactions for each particular transaction logging type, broken-do... | Use Cases | |
UC13 | A patient's DLHCP chooses to add or delete a patient's [E1, E2] personal representative by typing that person's MID [E1, E2].
| Use Cases | |
UC13E1 | The health care personnel types an invalid medical identification number and is prompted to try again.
| Use Cases | |
UC15E1 | The administrator types an invalid code information and is prompted to try again.
| Use Cases | |
UC15S1 | The administrator will maintain [add/update] a listing of allowable immunizations that an HCP can use. The administrator will store (1) the CPT code (The CPT code set accurately describes medical, surgical, and diagnostic services and is designed to communicate uniform information about medical services and procedures ... | Use Cases | |
UC15S2 | The administrator will maintain a listing of allowable diagnoses that an LHCP can use. The administrator will store (1) the ICD-9CM code (The International Statistical Classification of Diseases and Related Health Problems (most commonly known by the abbreviation ICD) provides codes to classify diseases and a wide vari... | Use Cases | |
UC15S3 | The administrator will maintain [add/update] a listing of allowable drugs that an HCP can use. The administrator will store (1) the National Drug Code (The National Drug Code (NDC) is a universal product identifier used in the United States for drugs intended for human use. National Drug Code Directory)
| Use Cases | |
UC15S4 | The administrator will maintain [add/update] a listing of allowable physical services (including laboratory procedures) that an HCP can use. The administrator will store information of a LOINC code (Logical Observation Identifiers Names and Codes (LOINC) is a database and universal standard for identifying medical labo... | Use Cases | |
UC16 | Through the Personal Health Records page, an LHCP chooses a chronic disease and a patient. The data in the database is analyzed according to the risk factors for the disease to determine if the patient exhibits a certain risk factor. Currently available risk factors for chronic diseases are defined for Diabetes and Typ... | Use Cases | |
UC16E1 | The LHCP chooses to examine a patient for which the preconditions do not apply (e.g., an adult shouldn't be tested for child diabetes) and the LHCP is prompted that no analysis can occur.
| Use Cases | |
UC17S1 | " An alive patient who has not had an office visit for more than one year and who has been diagnosed with
diabetes mellitus [is diagnosed with ICD code beginning with 250]
asthma [is diagnosed with ICD code beginning with 493], or
circulatory-system disease [is diagnosed with an ICD code between 390 and 459 inclusiv... | Use Cases | |
UC17S2 | An alive patient over 50 years old who has not had a flu shot [CPT codes 90656, 90658, 90660 per http://www.influenza.com/index.cfm?fa=ADDITIONAL_RES_HC_2 during the months Sept - Dec of the last calendar year (or during the months Sept - Dec of the current calendar year if the retrieval time is between Sept - Dec).
| Use Cases | |
UC17S3 | An alive patient under the age of 19 who has not had proper immunizations per the immunization schedule. The catch up schedule is relevant when the patient did not begin the immunizations according to the recommended schedule.
| Use Cases | |
UC18E1 | The administrator types an invalid hospital ID and is prompted to try again.
| Use Cases | |
UC18E2 | The administrator types an invalid hospital name and is prompted to try again.
| Use Cases | |
UC18S1 | The administrator will store (1) hospital Id number for the hospital [E1]; and (2) up to 30 alphanumeric characters giving the name of the hospital
| Use Cases | |
UC18S2 | The system shall enable the administrator to add a new entry for a hospital, or modify the hospital name in an existing entry. Note that the administrator is not allowed through the system interface to delete an existing entry or modify the hospital ID number in an existing entry.
| Use Cases | |
UC19E1 | The LHCP types an invalid medical identification number and is prompted to try again.
| Use Cases | |
UC19E2 | The patient chosen is not the desired patient. The LHCP does not confirm the selection and is prompted to try again.
| Use Cases | |
UC19S1 | The user (patient or personal health representative) can choose to view a list of (1) their own prescriptions or (2) the prescriptions for whom the user is a person health representative by choosing one patient from a a list of these patients. A prescription list is then displayed [S3], sorted by start date (the later ... | Use Cases | |
UC19S2 | The user (LHCP) selects a patient from the list of requested reports. At this point, the LHCP can view a prescription list for that patient [S3], sorted by start date (the later date is ranked earlier).
| Use Cases | |
UC19S3 | The prescription report is titled with the patient name. The prescription list includes medication, date prescribed, start date, end date for each prescription, and the name of the doctor who prescribed the medication.
| Use Cases | |
UC1E1 | The system prompts the enterer/editor to correct the format of a required data field because the input of that data field does not match that specified in data format 6.4 for patients.
| Use Cases | |
UC1E2 | The enterer/editor is presented with the name of the user and determines if it is invalid or not the right person. The enterer/editor is prompted to try again.
| Use Cases | |
UC1S1 | The HCP enters a patient as a new user of iTrust Medical Records system. Only the name and email are is provided. The patient's assigned MID and a secret key (the initial password) is personally provided to the user, with which the user can reset his/her password. The HCP can edit the patient according to data format 6... | Use Cases | |
UC1S2 | The HCP provides a deceased date (data format 6.4). An optional diagnosis code is entered as the cause of death.
| Use Cases | |
UC21E1 | The LHCP types an invalid medical identification number and is prompted to try again.
| Use Cases | |
UC21E2 | The patient chosen is not the desired patient. The LHCP or ER does not confirm the selection and is prompted to try again.
| Use Cases | |
UC21S1 | The LHCP or ER enters a MID [E1] and confirms the input [E2].
| Use Cases | |
UC22E1 | The user inputs invalid information and is prompted to try again.
| Use Cases | |
UC22E2 | The comment is empty and the text No Comment (without link) is displayed instead of the Read Comment link.
| Use Cases | |
UC22S1 | The system shall enable the administrator to (1) add a new entry for an appointment type, including its type name with up to 30 alpha characters and duration in the unit of minutes [E1], and (2) modify the duration in an existing entry [E1]. A new entry shall not have the same type name as that of any existing entry [E... | Use Cases | |
UC22S2 | The LHCP chooses to schedule an appointment with a patient (it is assumed that the LHCP and patient have already worked out the details of the appointment in person or via telephone outside of the system). The LHCP enters the patient MID, selects the type of appointment from a pull-down menu of the existing appointment... | Use Cases | |
UC22S3 | A user (an LHCP or patient) wishes to view a list of his or her upcoming appointments (i.e., a list including appointments whose appointment date and start time is equal or later than the current date/time). The user chooses to open his or her upcoming appointment list. Each row in the list includes the appointment typ... | Use Cases | |
UC23E1 | The LHCP types an invalid MID and is prompted to try again.
| Use Cases | |
UC23E2 | The chosen patient is not the desired patient. The LHCP does not confirm the selection and can try again.
| Use Cases | |
UC23S1 | The LHCP enters a patient medical identification number (MID) [E1] and confirms his/her input [E2].
| Use Cases | |
UC23S3 | " The LHCP can view of the comprehensive patient report for the specified patient, including the information below.
All patient demographic information (address, phone, etc.), see (UC4) and Data Format 6.1
The entire history of personal health records, see (UC10) and Data Format 6.4
All diagnoses, including those no... | Use Cases | |
UC23S4 | The LHCP views a list of requests he/she has made for reports, with the status and pertinent information about the requests.
| Use Cases | |
UC24 | "A patient or personal health representative can answer any of the following questions relative to a previous (in UC9, S1) office visit according to Data Format 6.13.
How many minutes did you wait in the waiting room?
How many minutes did you wait in the examination room before seeing your physician?
How satisfied ... | Use Cases | |
UC25 | "A user chooses to view physician satisfaction survey results. The user provides a zip code [E1] Or a hospital code and an (optional) physician type (from a pull-down list: see data format 6.2 - general, surgeon, heart specialist, pediatrician, OB/GYN). The patient is provided with the following for each physician of t... | Use Cases | |
UC25E1 | The input is not a valid zip code (see Data Format 6.2). The user is asked to try again.
| Use Cases | |
UC26E1 | The lab procedure code is not the intended lab procedure code. The HCP selects a different procedure code.
| Use Cases | |
UC26E2 | The selected Lab Technician is not the intended Lab Technician. The HCP selects a different Lab Technician.
| Use Cases | |
UC26S1 | An HCP can create a lab procedure for a given office visit. The HCP selects a procedure code, a priority from 1 to 3 (1=most important, 3=not as important), and Lab Technician (listed with his/her specialty and the number of pending lab procedures in his/her priority queue, grouped by priority). The HCP saves the new l... | Use Cases | |
UC26S2 | An HCP can view a previously created lab procedure for a given office visit. The HCP can view patient name, lab procedure code, current lab procedure status, timestamp, and Lab Technician name.
| Use Cases | |
UC26S3 | An HCP can reassign a previously created lab procedure to a different Lab Technician if the lab procedure is not yet in the testing state. The HCP selects a different Lab Technician from the list of available Lab Technicians (displayed with Lab Technician specialty and the number of pending lab procedures in his/her pr... | Use Cases | |
UC26S4 | An HCP can remove a previously created lab procedure for a given office visit. The HCP chooses to remove the lab procedure as long as the status is either in transit or received. The HCP is prompted to confirm that he/she wishes to remove the lab procedure.
| Use Cases | |
UC27S1 | The user has successfully changed his/her password (UC3, S2). An email informing the user of the password change is sent to the user including the MID but not the password.
| Use Cases | |
UC27S2 | The status of a laboratory procedure has been updated (UC26, S3). The patient is notified with the following information: the LOINC number and the updated status.
| Use Cases | |
UC28 | The LHCP chooses to view all patients with which he or she has ever had an office visit with. The patient¡¯s name (clickable to view PHR), address, and date of last office visit. The list is sorted by the date of the last office visit (most recent first).
| Use Cases | |
UC29 | A patient has just been diagnosed with a condition and wants to find the LHCPs in the area who have handled that condition. The patient chooses 'My Diagnoses¡± and is presented with a listing of all their own diagnoses, sorted by diagnosis date (more recent first). The patient can select a diagnosis and will be present... | Use Cases | |
UC2E2 | The enterer/editor is presented with the name of the user and determines if it is invalid or not the right person. The enterer/editor is prompted to try again.
| Use Cases | |
UC2S1 | An administrator enters a LHCP, ER, or public health agent as a user of iTrust Medical Records system, initially only the name and email are provided. A secret key is personally provided to the user, with which the user can reset his/her password. The admin must specify a specialty for a new LHCP (one of: General Physi... | Use Cases | |
UC2S2 | A LHCP enters an UAP as a user of iTrust Medical Records system according to data format 6.2 (all fields mandatory)
| Use Cases | |
UC30E1 | The HCP types an invalid medical identification number and is prompted to try again.
| Use Cases | |
UC30E2 | The patient chosen is not the desired patient. The HCP does not confirm the selection and is prompted to try again.
| Use Cases | |
UC30S1 | A patient or personal representative for a patient chooses to send a message to an LHCP (no multiple recipients allowed in a single message). The patient/representative is presented with a pull down menu of his/her DLHCP. The patient/representative chooses one of these DLHCP and types the subject (up to 100 characters... | Use Cases | |
UC30S2 | An LHCP chooses to send a message to a patient/representative (no multiple recipients allowed in a single message). The LHCP enters and confirms the patient/representative's MID [E1, E2]. The LHCP types the subject (up to 100 characters) and the text of a message (up to 1000 characters), and clicks the send button. A r... | Use Cases | |
UC30S3 | A patient or patient representative wishes to reply to a message. The patient/representative views his or her message inbox. The patient/representative opens the message to which he or she wishes to reply [S5], and then clicks the reply link above the message text. The patient/representative enters the text of the resp... | Use Cases | |
UC30S4 | An LHCP wishes to reply to a message. The LHCP views his or her message inbox. The LHCP opens the message to which he or she wishes to reply [S5], and then clicks the reply link above the message text. The LHCP enters the text of the response message (up to 1000 characters) he or she wishes to send, then clicks the sen... | Use Cases | |
UC30S5 | A user (a patient, patient representative, or LHCP) wishes to read a message from the message inbox or outbox. The user chooses to open his or her message inbox/outbox. Each row in the message inbox/outbox includes the message subject, the name of either the sender (only for the case of inbox) or recipient (only for th... | Use Cases | |
UC30S6 | A user (a patient, patient representative, or LHCP) can sort messages in his or her message inbox by either the sender's last name or timestamp (but not both) in either ascending or descending order (where timestamps in descending order would have the most recent first). A user can sort messages in his or her message o... | Use Cases | |
UC30S7 | A user (an LHCP or patient/representative) can modify his/her message displaying filter by modifying the following filtering criteria: (1) the sender (i.e., the sender's name is exactly the same as the specified string), (2) the subject (i.e., the subject is exactly the same as the specified string), (3) has the words ... | Use Cases | |
UC31S1 | The expired prescription report list is titled with the patient name. The expired prescription list includes medication, date prescribed (i.e., the day of the office visit), start date, end date for each prescription, and the name of the LHCP who prescribed the medication (where the name of the LHCP is linked to contac... | Use Cases | |
UC31S2 | The patient clicks on the name of the LHCP for an expired prescription, and is presented with the contact information for that LHCP (including First Name Last Name, LHCP Type, Street Address 1, Street Address 2, City, State, Zip Code, Phone, and Contact Email); if any type of contact information is missing or the whole... | Use Cases | |
UC32E1 | If there are no patients satisfying the three conditions, an empty list is presented.
| Use Cases | |
UC32S1 | "A chronic special-diagnosis-history patient is an alive patient who has been diagnosed with at least one of the following:
diabetes mellitus [is diagnosed with ICD code beginning with 250],
asthma [is diagnosed with ICD code beginning with 493], or
circulatory-system disease [is diagnosed with an ICD code between 3... | Use Cases | |
UC32S2 | The patient list is titled with the HCP's name. The patient list includes the patient's name (i.e., first name and last name), phone number, and contact email address [E1, E2] (so that confirmation calls or emails can be made or sent outside of the iTrust system). The list is sorted based on the ascending alphabetical ... | Use Cases | |
UC33E1 | The receiving HCP chosen is not the desired HCP. The sending HCP does not confirm the selection and is prompted to try again.
| Use Cases | |
UC33E2 | The patient, receiving HCP, referral notes, and/or referral priority are invalid, and the HCP is prompted to enter this information again.
| Use Cases | |
UC33S1 | An HCP chooses to refer a patient to another receiving HCP through the referral feature on a patient's office visit page (UC11). The sending HCP must select a receiving HCP by either entering the HCP's MID and confirming the selection, or by searching for the HCP by name. The sending HCP is also presented with a text b... | Use Cases | |
UC33S2 | An HCP chooses to view received referrals. The receiving HCP is presented with a list of referrals sorted by priority (from most important to least important). The receiving HCP then selects a referral to view details and is presented with the name and specialty of the sending HCP, the patient's name, the referral note... | Use Cases | |
UC33S3 | A sending HCP views a list of previously sent patient referrals. The HCP may sort the list of referrals by patient name, receiving HCP name, time generated, and/or priority. The HCP chooses a specific referral from the list to view complete details about the referral: patient name, receiving HCP name and specialty, tim... | Use Cases | |
UC34E1 | The patient chosen is not the desired patient. The HCP does not confirm the selection and is prompted to try again.
| Use Cases | |
UC34E2 | The patient, UAP, or personal representative enters a systolic blood pressure outside the range 40-240 or a diastolic blood pressure outside the range 40-150. He/she is notified of an error and is prompted to try again.
| Use Cases | |
UC34E3 | The patient, UAP, or personal representative enters a glucose level outside the range 0-250. He/she is notified of an error and is prompted to try again.
| Use Cases | |
UC34E4 | The patient, UAP, or personal representative tries to enter more than ten physiologic data points for one day and is told additional data cannot be entered.
| Use Cases | |
UC34S1 | An LHCP or UAP can add and delete patients from his or her monitoring list. A patient is added to the list by the LHCP or UAP typing in the patient's MID [E1] or name. An LHCP can delete a patient from his or her monitoring list by the LHCP typing the the patient's MID [E1]. In both cases, the LHCP is presented the nam... | Use Cases | |
UC34S2 | A patient whose at least one physiologic data type is specified to be under monitoring chooses to report their physiologic data. He or she can report his or her blood pressure (systolic and diastolic) [E2] and/or glucose levels [E3]. The input data, a timestamp, and the fact that the status is ¡°self-reported¡± are sav... | Use Cases | |
UC34S3 | An LHCP chooses to view the physiologic data monitoring details. The LHCP is presented with a listing of all his or her patients whose at least one physiologic data type is specified to be under monitoring with their blood pressure and glucose levels, recording timestamp, and whom reported the data (patient, UAP name, ... | Use Cases | |
UC34S4 | An LHCP selects to view additional information for a patient. The LHCP is presented with a screen upon which he/she can choose a date range. Once the date range is selected, the LHCP can see the patient name; patient phone number; personal representative (name and phone number), if applicable; and the blood pressure, g... | Use Cases | |
UC34S5 | A UAP can select to report physiologic measurements. He/she is presented with a list of the patients whose at least one physiologic data type is specified to be under monitoring and for whom he/she is allowed to report measurements. He or she can select a patient and then enter data. He or she can report the blood pres... | Use Cases | |
UC34S6 | A patient can select to report physiologic measurements for those whose at least one physiologic data type is specified to be under monitoring andfor whom he/she is a patient representative. He/she is presented with a list of the patients whose at least one physiologic data type is specified to be under monitoring and ... | Use Cases | |
UC35S1 | A patient is presented with a listing of all prescription drugs for which he/she has been prescribed and/or has taken in the last 12 months. The patient chooses one or more drug(s) for which to report the adverse event. The patient is then able to write a textual description which describes the symptoms of the adverse ... | Use Cases | |
UC35S2 | A patient is presented with a listing of all immunizations for which he/she has been administered in the last 12 months. The patient chooses the immunization for which to report the adverse event. The patient is then able to write a textual description which describes the symptoms of the adverse event and to save the i... | Use Cases | |
UC36S1 | A public health agent is presented with a listing of prescription drug-related adverse events for the time period that do not have a status of ¡°removed¡±, sorted by NDC. The public health agent can select to see the detail of a specific report. Upon reading the report, the public health agent can choose to send a ¡°fa... | Use Cases | |
UC36S2 | A public health agent is presented with a listing of immunization-related adverse events for the time period that do not have a status of ¡°removed¡±, sorted by CPT code . The public health agent can select to see the detail of a specific report. Upon reading the report, the public health agent can choose to send a ¡°f... | Use Cases | |
UC36S3 | The adverse event report changes to a status of ¡°removed.¡± A message of the removal is sent to the adverse event reporter and to the LHCP involved in the report (because the LHCP prescribed the drug or administered the immunization).
| Use Cases | |
UC37S1 | The drug desired to be prescribed is checked against the patient's drug allergies. The HCP is notified of drug allergy.
| Use Cases | |
UC37S2 | The drug desired to be prescribed is checked for interactions between other drugs currently taken by the patient. The HCP is notified of possible interactions.
| Use Cases | |
UC37S3 | The HCP selects one or more reasons out the nine reasons listed here for the overriding.[E1] The patient is sent a ¡°fake email¡± that the HCP has prescribed a medication that he/she is allergic to or that has a known interaction with a drug he/she is taking.
| Use Cases |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 8