Glossary

Clinical Information Systems (CIS)

Definition

A clinical information system (CIS) is software that captures, stores and shares patient clinical data, such as orders, results, medications and documentation, so clinicians can use it at the point of care. CIS is a broad category that includes EHRs, pharmacy, laboratory and radiology systems, and clinical decision support tools.

A CIS is the clinical side of a hospital's software, as opposed to its billing and administrative systems. It brings together the data clinicians need at the point of care, including readings from devices such as vital sign monitors, ventilators and infusion pumps.

What systems count as a clinical information system?

  • EHR clinical modules for documentation, orders and results
  • Computerized provider order entry (CPOE) and clinical decision support
  • Pharmacy and medication administration systems, including barcode scanning at the bedside
  • Laboratory information systems (LIS)
  • Radiology information systems (RIS) and PACS for images
  • Specialty systems for areas such as anesthesia, critical care, cardiology and oncology

How does a clinical information system help clinicians?

A CIS puts current information in one place: the chart, recent results, active medications and device readings. Built-in checks catch problems before they reach the patient, such as dose range alerts, duplicate therapy warnings and drug-allergy or drug-drug interaction checks. Shared records also make handoffs between shifts and departments easier, because everyone works from the same data.

What a CIS means for teams selling into healthcare

Many hospitals run most clinical modules inside their EHR platform, so new clinical software usually has to connect to it rather than replace it. Buyers include the CIO, the CMIO and CNIO, pharmacy and lab directors, and the clinical informatics team that maintains the system. Knowing which EHR a hospital runs tells you which integrations to lead with; see which EHRs US hospitals run.

CIS

See where CIS shows up on the accounts you sell to

Search 7.4M+ HCPs and 11M+ executives at 997K+ sites of care, each placed under its health system and IDN.

  • 30 days free
  • Self-serve
  • No credit card

Cookie settings

Turn each category on or off. Your choice is kept for 12 months and you can change it here at any time.

Necessary

Always on. Sign-in, security, downloads you asked for, your cookie choice, and the page that led to a signup.

View cookies (6)
  • dm_consentDmand AI. Your cookie choices and whether your browser sent a Global Privacy Control signal. 12 months.
  • dm_ft, dm_ltDmand AI. The first and the latest page you arrived on, with the date, so a signup is credited to the page that worked. 90 days, 30 days.
  • dm_fs, dm_lsDmand AI. The first and the latest source of a visit (a search engine, a campaign or the site that linked here). 90 days, 30 days.
  • dm_dl, dm_dl_okDmand AI. After you give an email address for a download, lets you download files without being asked again. 30 days.
  • Session and CSRF cookiesDmand AI (app.dmand.ai). Sign-in and form protection in the application. Session.
  • __cf_bm, cf_clearanceCloudflare. Tells people from automated traffic and keeps the site available. 30 minutes; cf_clearance while a security check is valid.

Analytics

On unless you turn it off. How pages are used, in aggregate, and recordings of how pages are used.

View cookies (6)
  • Google Tag ManagerGoogle. Loads the analytics and marketing tags that are on. Sets no cookie of its own and does not load when both categories are off. n/a.
  • _ga, _ga_<container-id>Google Analytics 4. Visits and page views in aggregate on dmand.ai. 2 years.
  • _clck, _clskMicrosoft Clarity. Recordings and heatmaps of how pages are used, with form fields masked. 1 year, 1 day.
  • CLID, MUID, ANONCHK, MR, SMMicrosoft (clarity.ms). Set by Microsoft when Clarity loads, to recognize a browser across sites that use Clarity. Up to 1 year.
  • None (cookieless)Ahrefs Analytics. Page views in aggregate. n/a.
  • ph_<project>_posthogPostHog. Product usage, errors and performance in app.dmand.ai, used to fix bugs and improve features. 365 days.

Marketing

On unless you turn it off, and always off when your browser sends a Global Privacy Control signal. A visitor identification service tells our sales team which companies and people visit.

View cookies (6)
  • _reb2buid, _reb2butkRB2B. Recognizes a returning browser for visitor identification. 360 days, 1 year.
  • _reb2bgeoRB2B. The location used to decide whether a visit can be identified. 20 days.
  • _reb2brefRB2B. The page or site that referred the visit. 15 days.
  • _reb2bfxf, _reb2btd, _reb2bliRB2B. Links the visit to an identified business profile. 1 month.
  • _reb2bresolveRB2B. Holds a match while it is being resolved. 2 days.
  • _reb2sessionID, _reb2bloadedRB2B. The current visit, and a guard against loading the script twice. 30 minutes, 1 second.

Functional

On unless you turn it off. Remembers choices such as a collapsed section.

View cookies (none today)