By Eric Andrew Kristof, RN, CAHIMS | Healthcare IT Professional | HIMSS Arkansas Chapter Member
About This Series: The HIMSS Word of The Day is a running blog series drawing from the HIMSS Dictionary of Health Information and Technology Terms, Acronyms, and Organizations, 6th Edition (2025) — the authoritative reference for healthcare IT professionals and the primary study resource for CAHIMS and CPHIMS certification. Each post paraphrases the term in plain language, grounds it in real-world healthcare IT context, and adds a bedside nursing perspective you won’t find in a textbook.
📖 The Term: JASON
Source: HIMSS Dictionary of Health Information and Technology Terms, Acronyms, and Organizations, 6th Edition (2025)
🔍 Plain-Language Definition
The HIMSS Dictionary describes JASON as an independent scientific advisory group that gives the U.S. government advice on defense, science, and technology. The Dictionary says the group began in 1960 and notes its 2014 publication on a robust health data infrastructure, which it links to a joint task force of the federal health IT standards and policy committees.
JASON is a name, not an acronym or a standard. A history of the group published by the Federation of American Scientists (FAS) also dates it to 1960 and describes it as an advisory panel whose work is largely classified, with some unclassified reports available online. One ONC slide deck dates the group’s consulting to 1959, so the start date varies by source.
The health IT report is A Robust Health Data Infrastructure. The front matter of the report says it was prepared by JASON at The MITRE Corporation for the Agency for Healthcare Research and Quality (AHRQ), under report number JSR-13-700 and AHRQ Publication No. 14-0041-EF. Its inner title page is dated November 2013, it was approved for publication on April 9, 2014, and its cover is dated April 2014. That is why some sources call it the 2013 report and others the 2014 report.
| Item | Detail |
|---|---|
| Group | JASON, an independent scientific advisory group |
| Report | A Robust Health Data Infrastructure |
| Prepared for | AHRQ |
| Dates | Title page November 2013; published April 2014 |
| Main idea | A shared architecture built on open standards and public APIs |
| Response | JASON Task Force final report, October 15, 2014 |
⚠️ Exam Alert: JASON is the advisory group, and JTF is the task force that responded to its report. AHRQ sponsored the report, and ONC is the federal health IT coordinator. FHIR and API are technical standards and tools, not organizations. The report is a recommendation document, not a regulation. HIMSS offers CAHIMS and CPHIMS.
🌐 Why It Matters: Real-World Healthcare IT Context
Because JASON is a body and a pair of policy documents, this section draws on the documents themselves, read directly for this post. They show what was proposed and argued. They are not independent evaluations of how the ideas worked out.
The report’s main argument. According to AHRQ’s page on the project and the report’s executive summary, the central finding is that incompatible data formats and poor interoperability among EHR systems are a major obstacle to exchanging health information. The report says this can be solved only with a comprehensive, transparent, overarching software architecture, and that better care and lower costs depend on using health data for both practice and research while protecting patient privacy.
The architecture principles. The report lists principles that now read like a preview of later debates: patients own their data, the design should not depend on a particular data type, platform, or storage location, and systems should use published APIs and open standards. It also calls for encryption of data at rest and in transit, with key management kept separate from data management. Data would carry metadata, context, and provenance, and be represented as small units with metadata attached. It also says a migration path from legacy EHR systems should be provided.
Privacy and recommendations. The report proposes a “patient privacy bundle,” a set of fine-grained default permissions that a patient could choose, with permissions attached to both data and metadata. Among its recommendations, ONC would define the overarching architecture within 12 months, EHR vendors would be required to develop and publish APIs, and the federal Meaningful Use program would use Stage 3 to require open APIs.
The task force response. The JASON Task Force (JTF) final report, dated October 15, 2014, responds to the JASON report. It agrees on an open-API foundation, on moving beyond document-centered exchange, and on using Meaningful Use Stage 3 as a pivot. It favors FHIR as the base standard and suggests ONC fund a faster standards process. It also disagrees with parts of the JASON assessment: it says existing EHR and financial systems do not need to be replaced, that JASON understated current progress, and that timelines ignore policy, legal, business, and cultural barriers. It prefers a loosely coupled “Coordinated Architecture” shaped by the market over top-down design, with regulation only as a fallback. The report also states that a public API does not mean data is exposed without regard to privacy and security, and it calls for standards-based authentication and authorization such as OAuth2.
What came later. ONC’s page on the Cures Act Final Rule, last updated April 1, 2026, says the rule asks industry to adopt standardized APIs so patients can use smartphone apps to get structured health information, and that patients must be able to access their electronic health information at no cost. The page’s description does not mention FHIR, though the JTF report named it. These two later facts show that the open-API idea moved from advice to rule, but this post does not claim that JASON alone caused that outcome.
The overall picture is of a report that set the direction, a task force that adjusted the pace and the method, and later federal rules that put APIs into regulation.
Common JASON report problems:
- Treating JASON as an acronym, a standard, or a software product
- Mixing up the JASON report with the JASON Task Force report
- Quoting the report as a 2013 or 2014 document without noting the title page and publication dates
- Assuming the report became federal policy as written
- Confusing AHRQ, which sponsored the report, with ONC, which coordinates federal health IT
- Reading the task force response as a rejection of open APIs, when it agreed with the direction
What supports a robust health data infrastructure:
- Published APIs and open standards that any developer can use
- Patient access to, and say over, their own data
- Encryption in transit and at rest, with key management kept separate
- Metadata and provenance that travel with the data
- A migration path from legacy systems
- Market coordination backed by clear federal levers such as certification
🏥 The Nurse’s Perspective: Clinical, Bedside, & Workflow
Most nurses never read a federal advisory report, but its questions show up in daily work: where data lives, who can see it, and how fast it moves.
At the Bedside
A principle such as “patients own their data” becomes concrete when a patient asks how to see test results on a phone or share a record with a new clinic. Nurses are often the first people patients ask. Knowing that patient access through apps is a policy goal, and that it is supported by federal rules, helps nurses answer with confidence and point patients to the right portal or support line.
In Clinical Workflow
Care teams still reconcile information that arrives in different formats from different systems. The report’s concern about incompatible formats matches what nurses see when an outside record arrives as a scanned document instead of data they can search. Nurse informaticists can use that experience to describe which pieces of information matter most when systems exchange data.
In EHR Implementation (Go-Live Perspective)
The migration path from legacy systems is not abstract at an Epic Go-Live, where conversion, interfaces, and downtime procedures all depend on how old and new records connect. Analysts at the elbow hear the consequences when a historical value does not display where nurses expect it. Careful notes on those cases help teams decide what to convert, what to link, and what to leave in an archive.
🎓 CAHIMS / CPHIMS & HIMSS Perspective
CAHIMS Exam Domain Mapping
JASON gives historical context for interoperability policy:
| CAHIMS Domain | How JASON Appears |
|---|---|
| Healthcare & Technology Environments | Federal advisory bodies, policy history, and the push for open APIs |
| Clinical Informatics | Data sharing for care and research, and patient access to records |
| Healthcare Information & Systems Management | Architecture principles, legacy migration, and API-based exchange |
| Management & Leadership | Policy debate, stakeholder disagreement, and change at the national level |
Key Terms to Know Alongside JASON
- API (Application Program Interface) — set of rules that lets one program request data or services from another
- FHIR (Fast Healthcare Interoperability Resources) — HL7 standard for exchanging health data using web technologies
- Argonaut Project — industry effort to speed development and adoption of FHIR-based APIs
- MU (Meaningful Use) — federal incentive program that required defined uses of certified EHR technology
- Interoperability — ability of systems to exchange and use information
- OAuth (Open Authorization) — standard for granting an application limited access to data
HIMSS Organizational Position
HIMSS offers education and research on health information and technology topics through its Resource Center. Members can find related information on the HIMSS Resource Center page.
🧭 More HIMSS Word of The Day Terms
Related terms in the Interoperability and Standards series:
- Health Information Exchange (HIE)
- UMDNS (Universal Medical Device Nomenclature System)
- HISP (Health Information Service Provider)
- QRDA (Quality Reporting Data Architecture)
Browse all Interoperability and Standards terms or the A–Z glossary.
🔗 Explore Further: External References
- AHRQ Digital Healthcare Research — A Robust Health Data Infrastructure https://digital.ahrq.gov/ahrq-funded-projects/robust-health-data-infrastructure
- JASON (2014), AHRQ Publication No. 14-0041-EF — A Robust Health Data Infrastructure (full report) https://www.healthit.gov/sites/default/files/ptp13-700hhs_white.pdf
- ONC — JASON Task Force Final Report, October 15, 2014 https://www.healthit.gov/sites/default/files/facas/Joint_HIPC_HITSC_JTF_Final%20Report_2014-10-15.pdf
- ONC (hosted) — A Robust Health Data Infrastructure, presentation slides by AHRQ, June 10, 2014 https://www.healthit.gov/sites/default/files/facas/hitpc_jasonreport_2014-06-10.pdf
- Federation of American Scientists — The Secret History of the JASON https://fas.org/publication/the_secret_history_of_the_jaso/
- ONC — Cures Act Final Rule https://healthit.gov/regulations/cures-act-final-rule/
- HIMSS — Resource Center https://www.himss.org/resource-center
Term source: HIMSS Dictionary of Health Information and Technology Terms, Acronyms, and Organizations, 6th Edition (2025). All definitions in this series are paraphrased for editorial purposes. Readers are encouraged to consult the primary source for exact language.
Eric Andrew Kristof, RN, CAHIMS is a Healthcare IT professional and HIMSS Arkansas Chapter member based in Hot Springs Village, AR, with hands-on Epic Go-Live experience and a diverse healthcare and IT background. He writes at kristof.org at the intersection of clinical care and healthcare technology.

Leave a Reply