Video: Every Case Tells a Story| Webinar: ACR/CHEST ILD Guidelines in Practice

An official publication of the ACR and the ARP serving rheumatologists and rheumatology professionals

  • Conditions
    • Axial Spondyloarthritis
    • Gout and Crystalline Arthritis
    • Myositis
    • Osteoarthritis and Bone Disorders
    • Pain Syndromes
    • Pediatric Conditions
    • Psoriatic Arthritis
    • Rheumatoid Arthritis
    • Sjögren’s Disease
    • Systemic Lupus Erythematosus
    • Systemic Sclerosis
    • Vasculitis
    • Other Rheumatic Conditions
  • FocusRheum
    • ANCA-Associated Vasculitis
    • Axial Spondyloarthritis
    • Gout
    • Psoriatic Arthritis
    • Rheumatoid Arthritis
    • Systemic Lupus Erythematosus
  • Guidance
    • Clinical Criteria/Guidelines
    • Ethics
    • Legal Updates
    • Legislation & Advocacy
    • Meeting Reports
      • ACR Convergence
      • Other ACR meetings
      • EULAR/Other
    • Research Rheum
  • Drug Updates
    • Analgesics
    • Biologics/DMARDs
  • Practice Support
    • Billing/Coding
    • EMRs
    • Facility
    • Insurance
    • QA/QI
    • Technology
    • Workforce
  • Opinion
    • Patient Perspective
    • Profiles
    • Rheuminations
      • Video
    • Speak Out Rheum
  • Career
    • ACR ExamRheum
    • Awards
    • Career Development
  • ACR
    • ACR Home
    • ACR Convergence
    • ACR Guidelines
    • Journals
      • ACR Open Rheumatology
      • Arthritis & Rheumatology
      • Arthritis Care & Research
    • From the College
    • Events/CME
    • President’s Perspective
  • Search

RheumCode: Creating a Common Rheumatology Language in EHRs

Allison Plitman, MPA, Tom Tack & Jason Liebowitz, MD  |  Issue: February 2025  |  November 25, 2024

“The model of creating structured data elements in a standardized format for EHRs has already been leveraged in the fields of cardiology and oncology. We are hoping to put rheumatology at the forefront of medicine with the use of this format and tool,” says Dr. Subash. “Imagine being able to compare similar patients in your clinic, or picture smoothly assuming care for a newly referred patient with all the data necessary to continue treatment—no faxes or calls to outside clinics required.”

The Oncology Model

The importance of RheumCode has both legislative context and technical precedent. The 21st Century Cures Act mandates improved patient accessibility to EHR data while ensuring patient privacy. The Fast Healthcare Interoperability Resources (FHIR) provides a modern framework for managing both structured and unstructured medical data in EHRs. Initially introduced in 2012 and now in its fourth iteration, FHIR is a widely used, standardized set of rules for representing and exchanging data among EHRs.

ad goes here:advert-1
ADVERTISEMENT
SCROLL TO CONTINUE

As a model in this area, RheumCode can look to an oncology initiative called mCode, which provides a structured approach to data standardization using FHIR. The successful implementation of mCode has highlighted the importance of “use cases” in creating relevant data structures. Other medical specialties, including cardiology and radiation oncology, are now developing similar data standards, a process that RheumCode plans to emulate.

Steps Forward

The RheumCode development team is taking a stepwise approach in moving forward with this initiative. The first step is to identify specific use cases for the tool to focus their development efforts. The team has defined some uses, including monitoring osteoporosis therapy and managing DMARD therapy, and is collecting input from the community about which use cases they would find most relevant for their own practices.

ad goes here:advert-2
ADVERTISEMENT
SCROLL TO CONTINUE

The next steps will be to define a RheumCode vocabulary and develop an implementation guide, detailing both essential and optional data elements. This guide will help standardize how data are collected across EHR systems.

The team also hopes to launch pilot projects with EHR systems, such as EPIC, to test the effectiveness of the developed tools and gather meaningful data. EPIC is generally open to pilot projects led by specialists and typically provides the necessary data elements to support the development of new tools that can be customized by individual sites.

The goal is to create a package that other institutions can use for their own pilot projects. Successful projects can demonstrate value and attract interest from other clinicians and potential investors, such as pharmaceutical companies. The RheumCode team is also exploring other funding options, such as grants from the National Institutes of Health, to support tool development and cover consulting costs.

Page: 1 2 3 | Single Page
Share: 

Filed under:EMRsPractice ManagementPractice Support Tagged with:electronic health records (EHRs)

Related Articles

    Electronic Health Records Present Communication Challenges for Physicians

    October 1, 2014

    Digitized patient records have transformed how clinicians record, understand clinical information

    Unwise Choices: EHRs, PBMs, Drug Costs Are Leading to Physician Burnout

    November 5, 2017

    My dear electronic health records How do I dislike thee? Let me count the ways Adaptation of Sonnet 43 By Elizabeth Barrett Browning, 1806–1861 As my tenure as physician editor winds down, it’s worth reviewing some of the more nettlesome issues confronting clinicians that have been previously discussed in these pages and gauge their current…

    Electronic Health Record Contracts Done Right

    June 10, 2012

    Consider both your practice’s needs and the long-term viability of the technology when selecting an EHR system.

    Measuring Up for Meaningful Use

    April 13, 2011

    The Centers for Medicare and Medicaid Services’ (CMS’) Electronic Health Record (EHR) Incentive Program—Meaningful Use—requires that eligible providers participating in the incentive program successfully demonstrate meaningful use of the EHR system by reporting on a set of core and menu functional objectives to qualify for incentive payments of up to $44,000.

  • About Us
  • Meet the Editors
  • Issue Archives
  • Contribute
  • Advertise
  • Contact Us
  • Copyright © 2025 by John Wiley & Sons, Inc. All rights reserved, including rights for text and data mining and training of artificial technologies or similar technologies. ISSN 1931-3268 (print). ISSN 1931-3209 (online).
  • DEI Statement
  • Privacy Policy
  • Terms of Use
  • Cookie Preferences