CAHIMS flashcards
CAHIMS · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Functional requirement
- A statement describing a behavior or capability the system must perform, such as calculating a weight-based dose or generating a discharge summary.
- Non-functional requirement
- A quality attribute or constraint on the system, such as response time, uptime, security controls, or concurrent-user capacity, rather than a specific behavior.
- Use case
- A description of a sequence of interactions between an external actor and the system that produces a measurable result of value to that actor.
- Actor
- A person, role, or external system that interacts with the system under analysis and sits outside the system boundary.
- Gap analysis
- A comparison of current-state and future-state processes or capabilities that identifies what is missing and must be built, purchased, or redesigned.
- Traceability matrix
- A table mapping each requirement to its design components, build items, and test cases so that coverage and impact of changes can be verified.
- Third normal form
- A table design state in which repeating groups and partial dependencies are removed and no non-key attribute depends on another non-key attribute.
- Interface specification
- A document defining the data elements, message format, trigger events, direction, timing, and error handling for data exchanged between two systems.
- User acceptance testing
- Testing performed by end users against real workflows to confirm the system meets business requirements before go-live approval.
- Regression testing
- Re-execution of previously passed tests after a change to confirm that existing functionality was not broken by the modification.
- CPOE
- Computerized provider order entry, the module where clinicians enter orders electronically, replacing handwritten or verbal orders and enabling order checks.
- eMAR
- The electronic medication administration record that documents each dose given, the administering clinician, and the time, linked to the originating order.
- Five rights
- The medication safety checks of right patient, right drug, right dose, right route, and right time that barcode scanning at administration supports.
- Clinical decision support
- Logic that combines patient data with a knowledge base to generate alerts, reminders, order sets, or documentation guidance at the point of care.
- Alert fatigue
- Desensitization caused by excessive or low-specificity warnings, producing high override rates and increased risk that important alerts are ignored.
- HL7 version 2
- A widely used messaging standard with pipe-delimited segments such as MSH, PID, and OBX, commonly carrying admissions, orders, and results between systems.
- FHIR
- A modern interoperability standard using modular resources exchanged over RESTful web services with JSON or XML payloads and standard HTTP verbs.
- SNOMED CT
- A comprehensive clinical terminology of concepts with hierarchical relationships, used to encode findings, diagnoses, and procedures in the electronic record.
- LOINC
- A terminology of standardized codes and names for laboratory tests and clinical observations that enables comparable results across systems.
- RxNorm
- A normalized naming and coding system for clinical drugs that links brand names, generic ingredients, strengths, and dose forms for medication interoperability.
- Protected health information
- Individually identifiable health information held or transmitted by a covered entity, subject to HIPAA privacy and security protections.
- Minimum necessary standard
- The HIPAA principle that use, disclosure, or request of protected health information should be limited to the least amount needed for the purpose.
- Health information exchange
- The electronic movement of health information among organizations according to national standards, supporting continuity of care across settings.
- Triple constraint
- The interdependent project dimensions of scope, time, and cost; changing one requires adjusting the others or accepting a change in quality.
- Critical path
- The longest-duration sequence of dependent activities in the schedule network, which determines the shortest possible project completion time.
- Float
- The amount of time an activity can be delayed without delaying the project finish; it equals late start minus early start.
- Cost variance
- Earned value minus actual cost; a negative value indicates the project has spent more than the value of work completed.
- Schedule performance index
- Earned value divided by planned value; a value below one indicates work is progressing slower than the baseline schedule planned.
- Estimate at completion
- The projected total cost of the project, often calculated as budget at completion divided by the cost performance index when current efficiency persists.
- Risk mitigation
- A threat response that reduces the probability or impact of a risk event before it occurs, such as redundancy or additional testing.
- RACI chart
- A responsibility matrix labeling each task as responsible, accountable, consulted, or informed, with exactly one accountable owner per task.
- Change control board
- The designated group that reviews change requests, assesses impact on scope, schedule, and cost, and approves or rejects them before baseline updates.