OSMR flashcards
OSMR · 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.
- Open-source license
- A legal grant allowing use, inspection, modification, and redistribution of source code under stated conditions, such as attribution, copyleft, or patent clauses.
- Copyleft obligation
- A license requirement that derivative works distributed to others carry the same license terms, so downstream recipients retain the same freedoms as the original.
- AGPL network clause
- A copyleft provision extending source-disclosure obligations to users who interact with the software over a network, even without distributing binaries.
- Structured report template
- A versioned definition of report sections, fields, and permitted values that constrains data entry and enables consistent downstream querying and aggregation.
- Regulated medical device status
- A determination based on intended use and jurisdiction; open-source licensing does not exempt clinical software from safety and market-approval requirements.
- HL7 v2 ORU message
- A pipe-delimited observation-result message carrying report content and coded values from a producing system to a receiving system in a defined trigger event.
- FHIR DiagnosticReport resource
- A RESTful resource representing a clinical report with references to patient, encounter, results, and presented-form attachments in JSON or XML.
- DICOM worklist
- A query mechanism supplying imaging modality worklists from a central system, linking scheduled studies to patients and later report references.
- Terminology binding
- The association of a data field with a controlled vocabulary and code system so values are comparable across systems and usable in decision support.
- Idempotent message handling
- A design property where repeated delivery of the same message, identified by its control ID, produces no duplicate record or side effect.
- Role-based access control
- An authorization model granting permissions to defined roles and assigning users to roles, so access derives from function rather than individual configuration.
- Break-glass access
- An emergency override granting temporary elevated access, which must be automatically logged, time-limited, and reviewed after the event.
- Tamper-evident audit log
- An append-only record protected by hash chaining or write-once storage so any alteration or deletion of prior entries becomes detectable.
- Data de-identification
- Removal or transformation of identifying elements, such as names, precise dates, and geographic subdivisions, so individuals cannot reasonably be re-identified.
- Recovery point objective
- The maximum acceptable amount of data loss measured in time, which sets the required backup frequency for a clinical system.
- Configuration as code
- Managing settings, templates, and interface mappings in version control so environments are reproducible and differences between them are auditable.
- Environment separation
- Maintaining distinct development, staging, and production systems, with production data excluded from lower environments unless properly de-identified.
- Rollback plan
- A documented, tested procedure for restoring the prior working state if a production change fails, including data and interface considerations.
- Traceability matrix
- A table mapping each requirement to its design elements, test cases, and recorded results, serving as primary validation evidence during audits.
- Clinical hazard analysis
- A structured process identifying failure modes that could harm patients, estimating severity and likelihood, and defining verified mitigating controls.
- User acceptance testing
- Structured testing by representative clinical users against real workflows, confirming the system meets operational needs before release approval.
- Regression suite
- A repeatable set of tests covering report rendering, coded values, access decisions, and interface parsing, rerun after every upgrade or change.
- Synthetic test data
- Artificially generated records that mimic realistic clinical content without deriving from actual patients, avoiding privacy exposure in test environments.
- License compatibility
- The analysis of whether code under different licenses can be combined and distributed, since conflicting copyleft terms may prohibit the combination.
- Software bill of materials
- An inventory of all components and their versions and licenses in a distribution, used to assess vulnerability exposure and attribution obligations.
- Total cost of ownership
- The full lifecycle cost of a deployment, including integration, customization, training, hosting, support, and upgrade labor beyond license fees.
- Project health indicators
- Observable signals of maintainability such as active maintainer count, release recency, issue response time, and presence of a security policy.
- Analytics denominator definition
- The explicit population, inclusion criteria, and observation window used to compute a rate, ensuring reported figures are interpretable and comparable.
- Event time versus refresh time
- The distinction between when a clinical event occurred and when a dashboard was last updated, preventing stale figures from being read as current.
- Small-cell suppression
- A disclosure control that hides aggregate counts below a threshold, and complementary cells where needed, to prevent re-identification of individuals.
- Secondary use governance
- Oversight of records reused for research or analytics, typically requiring ethics review plus consent, waiver, or de-identification before access.
- Data quality profiling
- Systematic checks of completeness, range validity, duplication, and cross-field consistency, reported alongside analytical results to qualify conclusions.