Information Systems

Question 1

What is static testing?

Answer 1

Reviewing the code itself

Question 2

What is dynamic testing?

Answer 2

Applying use case to the test code

Question 3

What is white box versus black box testing and for what are they used?

Answer 3

White Box = testing the inner working of the program e.g., Code Coverage. Great for debugging. The programmer will input many different things trying break the code. “Do this when x < 10: Programmer inputs 10, 11, a number, a letter, etc

Black Box = Tests functionality from end-user standpoint (may not find all bugs for all scenario)

Question 4

Describe the following Levels of Testing:

Answer 4

Unit Test: White box, code coverage, developer driven
Integration Test: white box, test interfaces/APIs, developer driven
System Test: Black Box Test Against Documented Requirements
Acceptance Test: Black Box, Request user sign-off (validation) Ex: beta test

Question 4

What is the College of American Pathologists (CAPs) Enterprise Clinical Information Management maturity model?

Answer 4

1) Controlled Content Ownership
2) structure and standardized data: priority clinical data are structured and controlled terminologies used
3) Data Capture: Practices in place to achieve high quality data input (e.g, device integration)
4) Analytics and data mining are performed on the data to enhance knowledge (knowledge)
5) Knowledge based quality improvement (wisdom)

Question 5

Define reliable Database Transactions:

Answer 5

ACID Test

Atomicity: transaction is indivisable–IT EITHER HAPPENS OR IT DOESN”T –NO PARTIAL TRANSACTIONS

Consistency: transaction meets all constraint rules (can’t add a DATE to an INT field, can’t have a non-unique PK)

Isolation: must be able to sequence simultaneous transactions. 2 transactions to update same cell–have to handle or else have “write-write failures)

Durability: must be tolerant to failure. Be able to deal with transactions in queue when system goes down

Question 6

What are the three levels of analytics?

Answer 6

Descriptive - reporting and querying of data to identify problems and solutions

Predictive - modeling, forecasting, and simulating outcomes based on the data

Prescriptive - recommend the best course of action based on the data (How can I achieve the best outcome?)

Question 7

Describe the difference between “functional” and “non-functional” requirements.

Answer 7

Functional Requirements are “What the system should do” A function is described as a set of inputs, the behavior, and outputs (see also software). Functional requirements may be calculations, technical details, data manipulation and processing and other specific functionality that define what a system is supposed to accomplish.

Non-Functional Requirements are “What the system should be” AKA: “Constraints” or”quality attributes”, “quality goals”, “quality of service requirements” and “non-behavioral requirements”.

• Safety or Factor of safety, Scalability (horizontal, vertical), Security
• Software, tools, standards etc. Compatibility
• Stability
• Supportability
• Testability
• Usability by target user community

Question 7

Describe tiers of Data Centers

Answer 7

Tier 1: Basic: single path for power, cooling–no redundancy (99.671 available).
Tier 2: redundant single path
Tier 3: more than one path but only one active at a time
Tier 4: multiples paths active at a time

Question 8

HIMSS EMR Adoption Model

Answer 8

Stage 0: no ancillaries
Stage 1: lab, pharmacy, rad
Stage 2: controlled vocabs, maybe document t imaging
Stage 3: flowsheets
Stage 4: CPOE
Stage 5: bar code med admin
Stage 6: phys doc
Stage 7: hIE and data warehouse

Question 9

Key stats on copy and paste

Answer 9

70-80% of physician notes contain copy and paste

Hammond 2003: 10% contained instance of high risk copying