Appendix A: Glossary

administrative staff: Individuals who manage people or data in a clinical setting.

allergy list: A series of allergies that a patient might have or from which a patient could be suffering.

bug: A repeatable problem in OpenMRS.

bug report: A report created describing a repeatable problem to software developers.

bundled module: An OpenMRS module that is included with a downloaded OpenMRS installation.

check digit: An extra digit that is added to the end of an identifier and depends on the rest of identifier.

clinician: A doctor, nurse, or other clinical officer who provides health care to patients.

cohort: A group of patients that can be defined by one or more common traits.

concept: The idea that encompasses any question which can be asked about a patient; an observable point of data.

concept class: A category of OpenMRS Concepts with associated traits.

concept datatype: A descriptor of the type of data which a given OpenMRS Concept describes (e.g., numeric, text, etc.).

concept dictionary: A list of all the medical and program-related terms used in OpenMRS as questions and answers.

customization: The idea of adapting a system to suit one's specific, particular needs.

data: A piece of knowledge that can be reduced to a single value.

demographics: Information about a person, typically including date of birth, location, name, etc.

drug: A specific formulation of a medication represented in OpenMRS.

electronic medical record: A computer system that allows for recording, storage, and retrieval of information related to the delivery of health care to patients.

encounter: A clinical transaction between a patient and one or more healthcare providers for the purpose of providing patient services or assessing the health status of the patient. An encounter happens at one point in time.

error: A message in a computer system that describe a problem currently or recently occurring.

flag: A visual indicator of certain criteria on a patient chart.

form: An electronic form that may be used for entering or viewing data.

Groovy: A computer scripting language that allows automation and quick performance of tasks.

implementation plan: A written document which details specific goals and tasks in installing, customizing, and using OpenMRS.

implementation team: A defined group of people working together to deploy OpenMRS in a specific project.

implementer: Someone who has or is in the process of deploying OpenMRS in a specific location or context of use.

informatics: The study of information technology applied to a specific domain.

internationalization: The adaptation an information system or pieces of information to be used in multiple locations.

IRC: Short for Internet Relay Chat, an online tool to communicate with others in "real time." OpenMRS uses IRC to allow developers and implementers to collaborate and meet.

local area network: A method of connecting multiple computers for communication over distances.

location: A physical place where a patient may receive healthcare services.

longitudinal: Having a goal of observing or trending over time.

mailing list: A collection of names and addresses used by a company to send material to multiple recipients. On the internet, mailing lists include each person's e-mail address rather than a postal address.

medical informatics: A discipline of studying the use of information technology in the field of medical science.

metadata: A piece of information that describes other information.

module: A software package that extends OpenMRS functionality in specific ways; often developed by others in the OpenMRS community.

module repository: An online resource to find and maintain community-developed OpenMRS add-on modules.

observation: One piece of information that is recorded about a person at a moment in time.

open source: A method of developing software where the source code is freely available for others to examine, use, and build upon. Also a type of software development community based around sharing of work and collaboration.

order: An action that a provider requests be taken regarding a patient.

patient: A person receiving health care services.

patient dashboard: A visual representation of a patient within OpenMRS, including his or her demographics and other important information.

patient identifier: Any unique number that can identify a patient. Examples are a Medical Record Number, a National ID, a Social Security Number, a driver's license number, etc.

person: Every individual who is referred to in any patient's record in OpenMRS must be stored in the system.

person attribute: store additional pieces of information about the people in your system in addition to those that are natively supported by OpenMRS.

pilot project: Actively planned as a test or trial.

platform: A computer system that is simple by design, intended to be customized and adapted for use in a wide variety of contexts.

privilege: A definition of what actions a user is allowed to take within OpenMRS.

problem list: A list of a patient's problems that serves as an index to his or her record. Each problem, the date when it was first noted, the treatment, and the desired outcome are added to the list as each becomes known. Thus the list provides an ongoing guide for reviewing the health status and planning the care of the patient.

profile: An OpenMRS user's basic information, including name, user ID, password, and language preferrence.

program: A planned series of administrative or research events.

program enrollment: Represents the fact that a patient is enrolled in one of these Programs over a time period at a Location.

provider: A health care professional, or group of health care professionals who provide a service to patients.

purge: To permanently delete data from the OpenMRS database.

relationship: A description of how two persons in OpenMRS are connected, e.g., mother and child.

retire: To make metadata unusable in the future while retaining it in OpenMRS for past reference.

role: Represents a group of privileges in OpenMRS.

sample data: Fictional, anonymized information representing patient care within OpenMRS. Some versions of the software include this artificial data to make it easier to plan an OpenMRS implementation.

SMART goals: Objectives for a project that are specific, measurable, attainable, realistic, and timely.

software developer: A person who is able to program customizations or additional functionality in OpenMRS.

state: A condition or situation; status.

super user: An OpenMRS user with permission to perform all management tasks in the application.

system administrator: A person who is responsible for day-to-day maintenance of a computer system or network.

uninterruptible power supply: A battery-based system that provides instant short-term power to a computer or other devices during a power outage.

unretire: To re-designate metadata as usable.

unvoid: Make data visible in OpenMRS that had previously been voided.

user: A person who uses OpenMRS, or more specifically the data in the system representing that person.

visit: A collection of one or more encounters that define an interaction between the patient and the healthcare system. Some common examples of visits include outpatient clinic visits, inpatient visits (hospitalization), and emergency room visits.

void: To mark data as deleted from a user perspective, but retain it in the OpenMRS database.

wiki: A web site containing documentation and other resources for a project or organization.

workflow: A series of tasks to accomplish a goal.

results matching ""

    No results matching ""