![\"athenahealth](\"https:\/\/emorphis.health\/blogs\/wp-content\/uploads\/2025\/12\/medical-banner-with-doctor-working-laptop-1024x683.webp\")
<\/p>\n
What Does the athenahealth Claude Integration Actually Bring to Healthcare?<\/strong><\/span><\/h2>See Contents<\/p>
- 1<\/span> What Does the athenahealth Claude Integration Actually Bring to Healthcare?<\/a><\/li>
- 2<\/span> Why This Development Could Change Patient Engagement<\/a><\/li>
- 3<\/span> Our Perspective: Patient Data Access Is Not the Same as Clinical Intelligence<\/a><\/li>
- 4<\/span> MCP and Healthcare Interoperability: Why This Technology Matters<\/a><\/li>
- 5<\/span> Patient Privacy Must Remain at the Center of AI Adoption<\/a><\/li>
- 6<\/span> Could AI Create More Work for Physicians Instead of Reducing It?<\/a><\/li>
- 7<\/span> What Healthcare Organizations Should Learn From This Announcement<\/a><\/li>
- 8<\/span> The Bigger Picture: Healthcare AI Needs Context, Not Just Connectivity<\/a><\/li><\/ul><\/div>\n\n
athenahealth’s new solution uses the Model Context Protocol (MCP) to connect its athenaOne platform with Anthropic’s Claude.<\/p>\n
The purpose is straightforward: allow patients to access and understand their medical information through natural language conversations.<\/p>\n
Patients using supported Claude Pro and Max accounts in the United States can add the athenaPatient MCP connector through their Claude settings. They authenticate using their athenahealth credentials and decide which information they want to share.<\/p>\n
With permission, Claude can retrieve information such as:<\/p>\n
\n\n\n- Laboratory results and vital signs.<\/li>\n
- Current medications and medical conditions.<\/li>\n
- Allergies and immunization records.<\/li>\n
- Previous consultations and visit history.<\/li>\n
- Diagnostic reports and medical procedures.<\/li>\n
- Care plans and other clinical information.<\/li>\n
- Patients can also revoke access to their information.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n
This is particularly relevant because people are already using AI assistants for health-related questions. An August 2026 Pew Research Center survey cited by athenahealth found that 34% of U.S. adults had used AI assistants for health-related purposes.<\/p>\n
The message is clear: patients are adopting AI whether healthcare organizations are ready or not.<\/p>\n
Instead of ignoring this behavior, healthcare technology providers need to create safer and more responsible ways for patients to interact with their medical information.<\/p>\n
![\"Custom-Development-and-integration,](\"https:\/\/emorphis.health\/blogs\/wp-content\/uploads\/2025\/06\/Custom-Development-and-integration-jpg.webp\")
<\/a><\/p>\nWhy This Development Could Change Patient Engagement<\/strong><\/span><\/h2>\nFor years, healthcare organizations have invested in patient portals and electronic health records. Yet, having access to medical information does not necessarily mean patients understand it.<\/p>\n
A patient might receive a laboratory report containing several unfamiliar medical terms. Another might forget medication instructions after leaving a consultation. Someone managing a chronic condition may need to review information from multiple appointments.<\/p>\n
These situations create opportunities for conversational AI.<\/p>\n
Consider a few practical examples:<\/p>\n
\n- Understanding laboratory reports:<\/strong> Patients could ask Claude to explain medical terminology and summarize what their available test results show.<\/li>\n
- Preparing for appointments:<\/strong> Patients could review previous visits, organize questions, and prepare for discussions with their physicians.<\/li>\n
- Understanding medications:<\/strong> Patients could use their records to review prescribed medications and understand documented instructions.<\/li>\n
- Reviewing medical history:<\/strong> Patients could request summaries of previous consultations, procedures, and diagnoses available in their records.<\/li>\n<\/ul>\n
These capabilities could make healthcare information easier to navigate.<\/p>\n
However, there is an important boundary. AI-generated explanations should not become independent diagnoses or treatment recommendations. Patients must continue consulting qualified healthcare professionals for medical decisions.<\/p>\n
The objective should be better-informed patients, not AI replacing physicians.<\/p>\n
Our Perspective: Patient Data Access Is Not the Same as Clinical Intelligence<\/strong><\/span><\/h2>\nAt Emorphis Health, we believe this is the most important point healthcare leaders should take away from the announcement.<\/p>\n
Giving AI access to patient records does not automatically make it clinically intelligent.\u00a0Healthcare information is complicated. Records can contain outdated medications, incomplete medical histories, duplicate entries, conflicting diagnoses, and information collected from different providers.<\/p>\n
Even accurate information can be misunderstood when it is separated from its clinical context.\u00a0For example, a laboratory result cannot always be interpreted independently. Its significance may depend on the patient’s age, medical history, existing conditions, medications, and previous test results.<\/p>\n
An AI assistant may generate a convincing explanation, but that does not guarantee clinical accuracy. This is why healthcare AI needs a strong technology foundation.\u00a0It needs reliable data integration, structured information exchange, data validation, appropriate access controls, and clinical oversight.<\/p>\n
We believe the next phase of healthcare innovation will be determined less by how many AI models organizations connect and more by how effectively they prepare their healthcare data for those models.<\/p>\n
Healthcare organizations must also understand how AI can work with fragmented clinical information. Our article on AI integration in healthcare<\/a> explains why connecting AI with existing healthcare systems is essential for achieving meaningful results.<\/p>\nMCP and Healthcare Interoperability: Why This Technology Matters<\/strong><\/span><\/h2>\nOne of the most interesting aspects of the athenahealth Claude integration is the use of the Model Context Protocol.<\/p>\n
MCP provides a standardized way for AI applications to connect with external systems and retrieve relevant information. In healthcare, this creates new possibilities for connecting AI assistants with authorized clinical data sources.<\/p>\n
Traditionally, healthcare organizations have relied on APIs, HL7 interfaces, and FHIR-based integrations to exchange information between systems.\u00a0MCP adds another layer to this technology landscape. It can help AI applications access relevant information through structured connections rather than depending entirely on manually uploaded documents or disconnected data sources.<\/p>\n
However, MCP should not be viewed as a replacement for established healthcare interoperability standards.<\/p>\n
Each standard has a different role:<\/p>\n
\n\n\n- HL7:<\/strong> Supports the exchange of healthcare information between clinical systems.<\/li>\n
- FHIR:<\/strong> Provides standardized resources and APIs for accessing and exchanging healthcare data.<\/li>\n
- DICOM:<\/strong> Supports the storage, management, and exchange of medical imaging information.<\/li>\n
- MCP:<\/strong> Provides a standardized way for AI applications to interact with external tools and authorized data sources.<\/li>\n
- PACS (Picture Archiving and Communication System): <\/strong>It is a medical imaging technology used to store, retrieve, manage, and share diagnostic images such as X-rays, CT scans, MRIs, and ultrasounds across healthcare facilities.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n
The opportunity is to bring these technologies together.<\/p>\n
Imagine an AI-powered healthcare application that can securely retrieve relevant information from an EHR, access laboratory results, understand diagnostic reports, and present a consolidated view of a patient’s available information.<\/p>\n
That is a much bigger opportunity than simply connecting a chatbot to a medical record.<\/p>\n
Healthcare organizations will need integration architectures that support these interactions while maintaining data consistency, security, and appropriate permissions.<\/p>\n
See Contents<\/p>
- 1<\/span> What Does the athenahealth Claude Integration Actually Bring to Healthcare?<\/a><\/li>
- 2<\/span> Why This Development Could Change Patient Engagement<\/a><\/li>
- 3<\/span> Our Perspective: Patient Data Access Is Not the Same as Clinical Intelligence<\/a><\/li>
- 4<\/span> MCP and Healthcare Interoperability: Why This Technology Matters<\/a><\/li>
- 5<\/span> Patient Privacy Must Remain at the Center of AI Adoption<\/a><\/li>
- 6<\/span> Could AI Create More Work for Physicians Instead of Reducing It?<\/a><\/li>
- 7<\/span> What Healthcare Organizations Should Learn From This Announcement<\/a><\/li>
- 8<\/span> The Bigger Picture: Healthcare AI Needs Context, Not Just Connectivity<\/a><\/li><\/ul><\/div>\n\n
athenahealth’s new solution uses the Model Context Protocol (MCP) to connect its athenaOne platform with Anthropic’s Claude.<\/p>\n
The purpose is straightforward: allow patients to access and understand their medical information through natural language conversations.<\/p>\n
Patients using supported Claude Pro and Max accounts in the United States can add the athenaPatient MCP connector through their Claude settings. They authenticate using their athenahealth credentials and decide which information they want to share.<\/p>\n
With permission, Claude can retrieve information such as:<\/p>\n
\n\n- \n
- Laboratory results and vital signs.<\/li>\n
- Current medications and medical conditions.<\/li>\n
- Allergies and immunization records.<\/li>\n
- Previous consultations and visit history.<\/li>\n
- Diagnostic reports and medical procedures.<\/li>\n
- Care plans and other clinical information.<\/li>\n
- Patients can also revoke access to their information.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n
This is particularly relevant because people are already using AI assistants for health-related questions. An August 2026 Pew Research Center survey cited by athenahealth found that 34% of U.S. adults had used AI assistants for health-related purposes.<\/p>\n
The message is clear: patients are adopting AI whether healthcare organizations are ready or not.<\/p>\n
Instead of ignoring this behavior, healthcare technology providers need to create safer and more responsible ways for patients to interact with their medical information.<\/p>\n
<\/a><\/p>\nWhy This Development Could Change Patient Engagement<\/strong><\/span><\/h2>\n
For years, healthcare organizations have invested in patient portals and electronic health records. Yet, having access to medical information does not necessarily mean patients understand it.<\/p>\n
A patient might receive a laboratory report containing several unfamiliar medical terms. Another might forget medication instructions after leaving a consultation. Someone managing a chronic condition may need to review information from multiple appointments.<\/p>\n
These situations create opportunities for conversational AI.<\/p>\n
Consider a few practical examples:<\/p>\n
- \n
- Understanding laboratory reports:<\/strong> Patients could ask Claude to explain medical terminology and summarize what their available test results show.<\/li>\n
- Preparing for appointments:<\/strong> Patients could review previous visits, organize questions, and prepare for discussions with their physicians.<\/li>\n
- Understanding medications:<\/strong> Patients could use their records to review prescribed medications and understand documented instructions.<\/li>\n
- Reviewing medical history:<\/strong> Patients could request summaries of previous consultations, procedures, and diagnoses available in their records.<\/li>\n<\/ul>\n
These capabilities could make healthcare information easier to navigate.<\/p>\n
However, there is an important boundary. AI-generated explanations should not become independent diagnoses or treatment recommendations. Patients must continue consulting qualified healthcare professionals for medical decisions.<\/p>\n
The objective should be better-informed patients, not AI replacing physicians.<\/p>\n
Our Perspective: Patient Data Access Is Not the Same as Clinical Intelligence<\/strong><\/span><\/h2>\n
At Emorphis Health, we believe this is the most important point healthcare leaders should take away from the announcement.<\/p>\n
Giving AI access to patient records does not automatically make it clinically intelligent.\u00a0Healthcare information is complicated. Records can contain outdated medications, incomplete medical histories, duplicate entries, conflicting diagnoses, and information collected from different providers.<\/p>\n
Even accurate information can be misunderstood when it is separated from its clinical context.\u00a0For example, a laboratory result cannot always be interpreted independently. Its significance may depend on the patient’s age, medical history, existing conditions, medications, and previous test results.<\/p>\n
An AI assistant may generate a convincing explanation, but that does not guarantee clinical accuracy. This is why healthcare AI needs a strong technology foundation.\u00a0It needs reliable data integration, structured information exchange, data validation, appropriate access controls, and clinical oversight.<\/p>\n
We believe the next phase of healthcare innovation will be determined less by how many AI models organizations connect and more by how effectively they prepare their healthcare data for those models.<\/p>\n
Healthcare organizations must also understand how AI can work with fragmented clinical information. Our article on AI integration in healthcare<\/a> explains why connecting AI with existing healthcare systems is essential for achieving meaningful results.<\/p>\n
MCP and Healthcare Interoperability: Why This Technology Matters<\/strong><\/span><\/h2>\n
One of the most interesting aspects of the athenahealth Claude integration is the use of the Model Context Protocol.<\/p>\n
MCP provides a standardized way for AI applications to connect with external systems and retrieve relevant information. In healthcare, this creates new possibilities for connecting AI assistants with authorized clinical data sources.<\/p>\n
Traditionally, healthcare organizations have relied on APIs, HL7 interfaces, and FHIR-based integrations to exchange information between systems.\u00a0MCP adds another layer to this technology landscape. It can help AI applications access relevant information through structured connections rather than depending entirely on manually uploaded documents or disconnected data sources.<\/p>\n
However, MCP should not be viewed as a replacement for established healthcare interoperability standards.<\/p>\n
Each standard has a different role:<\/p>\n
\n\n- \n
- HL7:<\/strong> Supports the exchange of healthcare information between clinical systems.<\/li>\n
- FHIR:<\/strong> Provides standardized resources and APIs for accessing and exchanging healthcare data.<\/li>\n
- DICOM:<\/strong> Supports the storage, management, and exchange of medical imaging information.<\/li>\n
- MCP:<\/strong> Provides a standardized way for AI applications to interact with external tools and authorized data sources.<\/li>\n
- PACS (Picture Archiving and Communication System): <\/strong>It is a medical imaging technology used to store, retrieve, manage, and share diagnostic images such as X-rays, CT scans, MRIs, and ultrasounds across healthcare facilities.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n
The opportunity is to bring these technologies together.<\/p>\n
Imagine an AI-powered healthcare application that can securely retrieve relevant information from an EHR, access laboratory results, understand diagnostic reports, and present a consolidated view of a patient’s available information.<\/p>\n
That is a much bigger opportunity than simply connecting a chatbot to a medical record.<\/p>\n
Healthcare organizations will need integration architectures that support these interactions while maintaining data consistency, security, and appropriate permissions.<\/p>\n
- FHIR:<\/strong> Provides standardized resources and APIs for accessing and exchanging healthcare data.<\/li>\n
- Preparing for appointments:<\/strong> Patients could review previous visits, organize questions, and prepare for discussions with their physicians.<\/li>\n
- Understanding laboratory reports:<\/strong> Patients could ask Claude to explain medical terminology and summarize what their available test results show.<\/li>\n
- 2<\/span> Why This Development Could Change Patient Engagement<\/a><\/li>
![\"athenahealth](\"https:\/\/emorphis.health\/blogs\/wp-content\/uploads\/2025\/06\/custom-1024x682.png\")
<\/p>\n