Ad Hoc Query and Rendering

http://hitontology.eu/ontology/EhrSfmAdHocQueryAndRendering an entity of type: FeatureClassified

Provide support for ad hoc query and report generation using tools internal or external to the system. Present customized views and summarized information from a patient's comprehensive EHR subject to jurisdictional laws and organizational policies related to privacy and confidentiality. The view may be arranged chronologically, by problem, or other parameters, and may be filtered or sorted. @en
Providers and administrators need to respond quickly to new requirements for data measurement and analysis. This may be as a result of new regulatory requirements or internal requirements. This requires that users be able to define their own query parameters and retain them. The data may be found in both structured and unstructured data. Providers and administrators also need to query for the absence of specific clinical or administrative data. For example, the Quality Control department may be reviewing whether or not the protocol for management of Diabetes Mellitus is being followed. If the protocol calls for fasting blood sugars every 3 months at minimum, the investigator might need to run an across-patient query locating patients with diabetes who do not show an FBS result within the last 3 months. Emergency Department benchmarking reports - Key point of time include arrival time; treatment area entrance time, MD contact time; decision to admit, discharge or transfer time; and departure (left ED) time. Important intervals include, but are not limited to the “door to doctor time”, “doctor to diction time”, “admission to bed availability or departure” as well as overall length of stayA key feature of an electronic health record is its ability to support the delivery of care by enabling prior information to be found and meaningfully displayed. EHR systems should facilitate search, filtering (e.g., filtering by key word, tagged data, or diagnosis), summarization, and presentation of available data needed for patient care. Systems should enable views to be customized, for example, specific data may be organized chronologically, by clinical category, by consultant, depending on need. The views may be arranged chronologically, by problem, or other parameters, and may be filtered or sorted. Jurisdictional laws and organizational policies that prohibit certain users from accessing certain patient information must be supported. @en

inverse relations

hito:OpenMrsFeatCohortQuery
↪ Cohort query