Choosing healthcare software is not simply a matter of finding a system that can store patient information, manage appointments, or help staff coordinate care. For a US homecare agency, healthcare software compliance means understanding how patient information is protected, which federal rules apply, and whether the software can exchange information safely with other healthcare systems. A platform may look professional and offer all the features an agency needs, but if it cannot demonstrate appropriate safeguards, support the necessary contractual obligations, or handle healthcare data consistently, it may create problems rather than solve them.

Homecare agencies handle sensitive information every day. Patient records, medical histories, care plans, medication information, visit notes, assessments, and communication between caregivers and office staff all need appropriate protection. Some of this information may be shared with physicians, hospitals, laboratories, insurance organizations, and other healthcare providers. That makes security and interoperability important considerations when selecting software.

HIPAA establishes federal requirements for protecting certain health information. HL7 and FHIR provide standards that help different healthcare systems exchange information. These are related concerns, but they serve different purposes. HIPAA addresses privacy and security obligations, while HL7 and FHIR address how healthcare information is structured and exchanged.

This guide explains what homecare agency owners should understand before choosing software that handles protected health information (PHI). It covers the current HIPAA requirements, the proposed Security Rule changes, the differences between HL7 v2 and FHIR, the importance of FHIR versions, and the specific questions worth asking a software vendor before signing an agreement.

1. What Healthcare Software Compliance Actually Means for a Buyer

Healthcare software compliance is often discussed as though it were a single feature that a vendor can switch on. In practice, it involves several distinct responsibilities, standards, technical controls, and contractual arrangements.

For a homecare agency owner, the most useful way to approach compliance is to think in terms of things that can be identified, documented, and verified.

Instead of asking a vendor whether its platform is secure, ask which safeguards it implements. Instead of accepting a general statement that the software supports healthcare interoperability, ask which HL7 or FHIR version it uses. Instead of assuming that patient information is protected because it is stored in the cloud, ask whether the provider signs a Business Associate Agreement and how it protects electronic protected health information.

These questions make a significant difference because different vendors can use the same general language while offering very different levels of technical detail.

Compliance is not a badge. It is a collection of identifiable obligations and safeguards.

Understanding the three parts of the decision

A buyer should evaluate healthcare software across three connected areas.

1. Legal and regulatory responsibilities

HIPAA establishes requirements for covered entities and business associates that handle protected health information. These requirements include privacy protections, security safeguards, business associate arrangements, and breach notification procedures.

A homecare agency should understand whether it is a covered entity and which vendors act as its business associates.

It should also understand the difference between the HIPAA Privacy Rule, the Security Rule, and the Breach Notification Rule. Each addresses a different part of protecting patient information.

2. Technical security controls

Software must have appropriate technical safeguards to protect electronic protected health information (ePHI).

These include identifiable controls such as:

Not every technical specification is explicitly mandated by HIPAA. Some implementation specifications are classified as addressable, meaning the organization must assess whether they are reasonable and appropriate and document its decision.

Other specifications, such as AES-256 encryption and immutable audit logs, can be included in a buyer’s procurement requirements even though HIPAA does not prescribe them by name.

3. Healthcare interoperability

Healthcare software rarely operates entirely on its own.

A homecare agency may need to exchange patient information with hospitals, physicians, laboratories, health information networks, or other healthcare organizations.

HL7 and FHIR standards help make these exchanges more consistent.

A vendor claiming to support FHIR should identify the actual version it supports, the relevant implementation guides, and the integrations that have been tested.

The distinction matters because a general claim of FHIR compatibility does not establish that two systems can exchange information successfully.

What a buyer should be able to verify

Before choosing a platform, an agency should be able to obtain clear answers to questions such as:

A vendor does not need to use complicated language to answer these questions. In fact, clear explanations are preferable.

The important point is that compliance should be supported by documented arrangements and identifiable technical controls, not simply by marketing language.

For a broader look at the healthcare-specific software requirements involved in this area, see our guide to HIPAA-compliant homecare software.

If you are scoping a homecare platform, our overview of home care software development covers the features agencies usually need first.

2. HIPAA in Plain Terms

HIPAA stands for the Health Insurance Portability and Accountability Act. For healthcare organizations, it establishes federal requirements concerning protected health information, including how it may be used, disclosed, and safeguarded.

For a homecare agency choosing software, understanding HIPAA begins with three questions:

  1. Does the organization fall under HIPAA?
  2. What information is protected?
  3. What responsibilities apply when software vendors handle that information?

Who does HIPAA cover?

HIPAA applies to covered entities and business associates.

Covered entities generally include:

A homecare agency that meets the applicable definition of a covered healthcare provider is a covered entity.

For example, an agency providing healthcare services and conducting covered electronic transactions may be subject to HIPAA requirements.

Business associates are individuals or organizations that perform certain functions or services on behalf of a covered entity and create, receive, maintain, or transmit protected health information in connection with those services.

Examples can include:

The relationship matters because a vendor does not need to provide direct medical care to become a business associate.

A software provider that stores patient information, processes care records, or maintains an electronic system containing PHI may qualify as a business associate.

What counts as protected health information?

Protected health information, commonly called PHI, is individually identifiable health information held or transmitted by a covered entity or business associate, subject to HIPAA’s definitions and exclusions.

It can include information relating to:

Information can also identify the individual through details such as their name, address, date of birth, contact information, or other identifying characteristics.

For a homecare agency, PHI can appear in several parts of everyday operations.

A caregiver might enter a patient’s condition after a home visit. An administrator might update the patient’s care plan. A nurse might document an assessment. An office employee might communicate with a physician about a change in the patient’s needs.

These records can contain PHI even when they are not part of a traditional hospital medical record.

Electronic protected health information, or ePHI, refers to PHI that is created, received, maintained, or transmitted electronically.

This is particularly relevant when an agency uses software to manage patient records, scheduling, documentation, communications, or care coordination.

The HIPAA Privacy Rule: who may see patient information?

The Privacy Rule establishes requirements governing the use and disclosure of PHI.

Its purpose is to protect patient information while allowing appropriate information sharing for healthcare operations and other permitted purposes.

A homecare agency should understand that patient information cannot simply be made available to every employee or outside organization because it is stored in an internal software platform.

Access and disclosure must have an appropriate basis under HIPAA.

For example, a caregiver may need information about an assigned patient’s care requirements. An administrator may need access to certain records for operational responsibilities. A billing employee may need information relevant to processing healthcare claims.

These employees do not necessarily need access to every record or every category of information in the system.

The Privacy Rule’s minimum necessary standard generally requires covered entities to make reasonable efforts to limit PHI use, disclosure, and requests to the minimum necessary for the intended purpose, subject to applicable exceptions.

This is why user permissions matter.

A healthcare software platform should help an agency establish appropriate access restrictions rather than treating every employee as though they have identical responsibilities.

The software should also make it possible to manage access when employees change roles or leave the organization.

The HIPAA Security Rule: three safeguard families

The Security Rule establishes requirements for protecting electronic protected health information.

It organizes safeguards into three categories: administrative, physical, and technical.

Administrative safeguards

Administrative safeguards concern the policies, procedures, and organizational responsibilities used to protect ePHI.

They include activities such as:

For a homecare agency, administrative safeguards involve deciding who is responsible for protecting patient information and establishing procedures that employees are expected to follow.

For example, an agency should have a process for removing access when an employee leaves and for reviewing unusual access to patient records.

Software can support these activities, but purchasing software does not replace the agency’s own administrative responsibilities.

Physical safeguards

Physical safeguards concern access to facilities, equipment, and workstations containing ePHI.

Examples include:

Homecare agencies should consider both office-based and mobile working environments.

Staff may use computers at an agency office, tablets during visits, or other authorized devices to access patient information.

The organization should consider how those devices are protected, who can use them, and what happens if a device is lost or stolen.

Technical safeguards

Technical safeguards concern the technology used to control access to ePHI and protect it while it is stored or transmitted.

Relevant controls include:

These are particularly important when comparing healthcare software platforms.

A vendor should be able to explain how its system identifies individual users, restricts access, records activity, and protects information exchanged between users and systems.

Required versus addressable: an important distinction

HIPAA does not treat every implementation specification in exactly the same way.

Some specifications are required. Others are addressable.

A required implementation specification must be implemented.

An addressable implementation specification requires the regulated organization to assess whether the specification is reasonable and appropriate in its circumstances.

If it is reasonable and appropriate, the organization must implement it.

If it is not, the organization must document that determination and implement an equivalent alternative measure when reasonable and appropriate, or document why no such alternative is reasonable and appropriate.

Addressable does not mean that an organization can ignore a security issue without considering it.

Encryption and automatic logoff are examples of addressable implementation specifications under the current Security Rule.

This distinction is particularly important when discussing encryption with software vendors.

HIPAA requires appropriate security safeguards, but the current Security Rule does not universally prescribe AES-256 as the mandatory encryption algorithm for every healthcare software platform.

A buyer can still require AES-256 encryption as a procurement specification.

The distinction is between what the regulation explicitly requires and what the agency chooses to require from its technology providers as part of its security expectations.

The Breach Notification Rule: the 60-day requirement

The HIPAA Breach Notification Rule establishes notification obligations following breaches of unsecured protected health information.

Under 45 CFR 164.404, a covered entity must notify affected individuals without unreasonable delay and no later than 60 calendar days after discovering a breach of unsecured PHI.

Additional notification requirements may apply to HHS and, in certain circumstances, the media.

The 60-day period is the outside deadline for individual notification. It should not be interpreted as permission to delay notification unnecessarily.

For a homecare agency, the practical lesson is that its software provider should have an established security incident process.

The agency should understand how the vendor identifies and reports incidents, how the parties communicate during an investigation, and how the vendor meets its contractual obligations.

A software agreement should address these responsibilities rather than leaving them unclear until an incident occurs.

How long must HIPAA documentation be retained?

HIPAA’s Security Rule also contains a documentation retention requirement.

Under 45 CFR 164.316(b)(2)(i), required Security Rule documentation must generally be retained for six years from the date of its creation or the date when it was last in effect, whichever is later.

This applies to required policies, procedures, and documented actions, activities, or assessments.

It is important not to confuse this requirement with medical-record retention.

The six-year Security Rule documentation requirement is not a blanket federal requirement that every patient medical record must be retained for six years.

Medical-record retention can depend on other federal requirements, state laws, payer rules, and the type of healthcare record.

An agency should therefore establish its documentation and patient-record retention policies separately, taking applicable requirements into account.

3. The Security Rule Update: What Is Proposed and What Is Actually in Force?

The HIPAA Security Rule is undergoing a proposed modernization intended to strengthen cybersecurity protections for electronic protected health information.

For healthcare business owners, the important issue is not simply what the proposed rule contains. It is understanding the difference between the proposal and the regulation that applies today.

Confusing those two things can lead to poor software decisions and misleading vendor conversations.

How the proposed update began

On 27 December 2024, the HHS Office for Civil Rights issued a Notice of Proposed Rulemaking titled HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information.

The proposal was published in the Federal Register on 6 January 2025.

The public comment period closed on 7 March 2025.

The purpose of the proposal was to strengthen the existing Security Rule and make several cybersecurity protections more explicit.

These included stronger requirements concerning authentication, encryption, risk analysis, system inventories, network documentation, incident response, and business associate oversight.

However, publication of a Notice of Proposed Rulemaking does not make its proposed provisions effective law.

A proposed rule is part of the federal regulatory process. It can be reviewed, changed, delayed, or finalized through subsequent agency action.

That distinction is essential when choosing software.

The May 2026 target and the July 2027 projection

The regulatory timeline has also changed.

The earlier regulatory agenda listed May 2026 as the anticipated final-action date.

That date passed without the proposal becoming an effective final rule.

The 2026 Unified Agenda subsequently placed the rulemaking under Long-Term Actions and listed July 2027 as the anticipated final-action date.

This is an agency planning estimate, not a guaranteed publication date or a statutory deadline.

The practical conclusion is that homecare agencies should not make purchasing decisions based on the assumption that the proposed changes have already become law.

The current Security Rule remains the applicable regulatory baseline while the rulemaking proceeds.

The proposal may eventually result in a final regulation, but its requirements should continue to be described as proposed until the applicable final rule is published and becomes effective.

What the proposed Security Rule would add

Although the proposed changes are not currently in force simply because they appeared in the NPRM, they provide useful information about the direction of federal cybersecurity expectations.

A homecare agency can understand these proposals and use them when evaluating whether a software platform has appropriate security capabilities.

The following are proposed additions, not a list of newly effective universal requirements under the current Security Rule.

1. Proposed mandatory multi-factor authentication

The proposal would make multi-factor authentication a more explicit requirement for relevant technology assets and actions involving changes to user privileges, subject to specified exceptions.

MFA requires users to provide more than one form of authentication.

For example, an employee might enter a password and then verify their identity through an authentication application.

For a homecare agency, this can provide additional protection if a password is compromised.

The existing Security Rule does not establish MFA as a general express requirement for every system. Nevertheless, it is a sensible security capability to request from a software vendor.

2. Proposed encryption requirements

The proposal would make encryption of ePHI at rest and in transit a more explicit requirement, subject to limited exceptions.

Encryption at rest protects information stored in databases, files, and other storage environments.

Encryption in transit protects information while it moves between systems, devices, and services.

The current Security Rule treats encryption as an addressable implementation specification.

That does not mean encryption is unimportant or that a healthcare organization can disregard it. The organization must assess its circumstances and document its decisions under the current requirements.

The proposed change would make the expectation more explicit.

3. Proposed technology asset inventories

The proposal would require more explicit documentation of technology assets relevant to ePHI.

An asset inventory helps an organization understand which devices, applications, systems, and other technology resources are involved in storing, processing, or transmitting protected health information.

For an agency, this is important because patient information may move through several connected systems.

Knowing where information is stored and which systems can access it makes security management more practical.

4. Proposed network mapping

The proposed rule would also require documentation of relevant network connections and the movement of ePHI.

This would help organizations understand how their systems communicate and where patient information travels.

For example, an agency may use one platform for patient records and another service for related healthcare functions.

A network map can help establish how those systems connect and where information is exchanged.

5. Proposed annual penetration testing

The proposal would require penetration testing at least once every 12 months, or more frequently when the risk analysis indicates that a shorter interval is necessary.

Penetration testing involves evaluating systems for security weaknesses by attempting to identify or exploit vulnerabilities through controlled testing.

This is different from simply running a basic automated security scan.

For a software buyer, the relevant question is whether the vendor can explain its testing approach and provide appropriate evidence of its security assessment activities.

6. Proposed more detailed risk analysis

The proposal would strengthen documentation and risk-analysis requirements.

A risk analysis helps an organization identify where ePHI could be exposed, which threats and vulnerabilities exist, and what safeguards are needed.

This should not be treated as a one-time administrative exercise.

Changes to technology, staff responsibilities, system access, and information flows can affect an organization’s security risks.

The proposed changes would make several of these expectations more explicit.

7. Proposed written incident-response plans

The proposal would require written security incident-response plans and procedures.

It would also require the plans to be reviewed and tested at least once every 12 months, with the results documented.

For a homecare agency, an incident-response plan should establish who is responsible for responding to security events and how the organization will investigate and manage them.

The software vendor’s own incident procedures are relevant, but they do not replace the agency’s responsibility to maintain appropriate organizational procedures.

8. Proposed business associate verification

The proposal would strengthen oversight of business associates.

It would require written verification that business associates have implemented required technical safeguards, with verification at least annually.

This is an important distinction from simply obtaining a signed BAA.

A BAA establishes contractual responsibilities, but it does not independently demonstrate that a vendor has implemented effective security controls.

The proposed verification requirements would make that distinction more explicit.

What this means when choosing software today

The buyer’s lesson is straightforward: do not confuse a proposed rule with an effective regulation, and do not accept a vendor’s claim that the new requirements are already law.

If a vendor tells an agency that every provision in the 2025 NPRM is already a mandatory HIPAA requirement, that is a reason to ask for clarification.

The agency should also avoid going to the opposite extreme and ignoring the proposal because it has not yet been finalized.

Many of the proposed controls are sensible security practices even under the current regulatory framework.

For example:

These are reasonable capabilities to consider when evaluating healthcare software.

The most practical approach is to choose a platform that can demonstrate appropriate current safeguards and has a clear security-development approach for future regulatory changes.

An agency should not rely on a vendor’s prediction about when the final rule will appear. It should ask what the system actually does today, what documentation is available, and how the vendor intends to address changes in applicable requirements.

4. HL7 v2 vs FHIR: Messages vs APIs, in Plain Terms

HIPAA explains how protected health information must be handled. HL7 and FHIR address a different question: how can different healthcare systems exchange information in a consistent way?

This matters because homecare agencies do not always work with information that originates inside their own software.

A patient may be referred from a hospital. A physician may send clinical information. A laboratory may provide test results. Another healthcare organization may need information about a patient’s care.

If the systems involved use different data formats and communication methods, exchanging information can become difficult.

Healthcare interoperability standards help address that problem.

Two important standards in this area are HL7 Version 2 and Fast Healthcare Interoperability Resources, commonly called FHIR.

What is HL7 v2?

HL7 Version 2 is an established healthcare information-exchange standard.

It uses structured messages to communicate information between healthcare systems.

Think of it as a standardized electronic message sent from one system to another.

A hospital registration system, for example, might send a message to another connected system when a patient is admitted, discharged, or transferred.

A laboratory system might send a message containing test results.

The receiving system interprets the message according to the defined structure.

HL7 v2 commonly uses segments and fields to organize information.

Examples of healthcare activities supported by HL7 v2 messaging include:

HL7 v2 remains widely used in healthcare, particularly in established hospital and clinical environments.

This means an agency should not assume that older healthcare integrations have disappeared simply because newer interoperability standards are available.

If a homecare platform needs to connect with an existing hospital or healthcare information system, HL7 v2 may still be relevant.

What is FHIR?

FHIR stands for Fast Healthcare Interoperability Resources.

It is a newer HL7 standard designed to make healthcare information exchange more consistent and accessible through modern technical approaches.

One of its important features is support for RESTful APIs.

An API allows one software system to request information or perform supported operations through a defined interface.

Rather than relying only on large structured messages, FHIR organizes healthcare information into standardized resources.

Some important examples include:

Patient — The Patient resource represents information about an individual receiving healthcare services. It can include demographic and identifying information.

Observation — The Observation resource represents measurements and clinical observations. Examples can include vital signs, laboratory results, and other recorded clinical measurements.

Encounter — The Encounter resource represents an interaction between a patient and a healthcare provider.

Practitioner — The Practitioner resource represents a healthcare professional involved in providing services.

Appointment — The Appointment resource represents a scheduled healthcare event.

MedicationRequest — The MedicationRequest resource represents a request or order for medication.

These standardized resources make it easier for different systems to work with information using a shared structure.

However, FHIR is not limited exclusively to REST APIs. The specification also supports other approaches, including messaging and document-based exchange.

The practical difference between HL7 v2 and FHIR

The easiest way to understand the distinction is to think about how information moves.

With HL7 v2, one system sends a structured message to another system.

With FHIR, systems can use standardized resources and API interactions to request, retrieve, or exchange healthcare information.

AreaHL7 v2FHIR
Main approachStructured messagesStandardized resources
Typical exchangeSystem-to-system messagesAPI-based interactions and other exchange methods
Data structureSegments and fieldsResources and elements
ExamplesAdmissions and laboratory messagesPatient, Observation, Encounter
Healthcare useEstablished healthcare interfacesModern interoperability and API integrations

Neither standard should automatically be treated as a replacement for the other in every healthcare environment.

A healthcare organization may operate systems using HL7 v2 while introducing FHIR-based integrations for other services.

For a homecare agency, this means the software should be evaluated against the systems it actually needs to communicate with.

Why interoperability matters to homecare agencies

Homecare services depend on accurate information about the patient and the care being provided.

A platform that supports appropriate interoperability can help an agency exchange information with other healthcare organizations through supported interfaces.

For example, a homecare provider may need to receive information related to a patient referral or share appropriate clinical information with another authorized provider.

The important issue is whether the software can exchange the required information using a format and version that the receiving system supports.

A vendor saying that its platform supports HL7 or FHIR is only the beginning of the conversation.

The agency should ask which standard, version, implementation guide, and specific integration capabilities are supported.

5. FHIR Versions: Why R4, R5, and R6 Matter

Knowing that a healthcare software platform supports FHIR is useful, but it does not tell an agency everything it needs to know.

FHIR has multiple versions, and different healthcare systems may support different versions.

For US healthcare software buyers, this distinction is especially important because the established federal interoperability specifications examined in this research are based on FHIR R4.

The existence of a newer published version does not automatically mean it is the version a homecare agency should select.

FHIR R4: the established US baseline

FHIR R4 is the established foundation for many US healthcare interoperability implementations.

There is an important historical distinction between R4.0.0 and R4.0.1.

FHIR R4.0.0 was released on 27 December 2018 and was the first FHIR release containing normative content.

FHIR R4.0.1 was published on 30 October 2019. It introduced technical corrections without substantively changing the normative content of R4.

R4.0.1 is therefore the version commonly referenced in US interoperability specifications.

This matters because a healthcare software vendor should be able to explain whether its FHIR implementation supports R4.0.1 rather than simply saying that it supports FHIR.

How US Core relates to R4

US Core is a US-specific FHIR Implementation Guide.

It establishes additional requirements and constraints that help healthcare systems exchange information consistently.

FHIR provides the underlying resource framework. An implementation guide defines how those resources should be used in a particular context.

US Core 6.1.0 is based on FHIR R4 and corresponds to USCDI version 3.

The Office of the National Coordinator for Health Information Technology identified US Core 6.1.0 as ready for adoption in Certified Health IT under the HTI-1 Final Rule.

HTI-1 adopted USCDI v3 as the baseline data standard within the ONC Health IT Certification Program, with the relevant date of 1 January 2026.

However, these regulatory details need to be interpreted correctly.

They do not mean that every homecare agency independently became legally required to implement US Core 6.1.0 on that date.

USCDI, US Core, and the ONC Health IT Certification Program have specific regulatory and technical roles.

ONC also issued subsequent guidance concerning enforcement discretion and USCDI v3.1.

For an agency choosing software, the useful point is that US Core 6.1.0 provides an important reference for R4-based US healthcare interoperability.

CMS-0057-F and FHIR R4

Another important federal development is the CMS Interoperability and Prior Authorization Final Rule, known as CMS-0057-F.

Published on 17 January 2024, the rule establishes interoperability and prior authorization requirements for specified payer organizations and programs.

The rule identifies FHIR R4.0.1 and US Core Implementation Guide STU 3.1.1 among its technical standards.

Affected organizations include specified Medicare Advantage organizations, Medicaid and CHIP programs, Medicaid managed-care plans, and certain Qualified Health Plan issuers on federally facilitated exchanges.

The rule is relevant to the broader US healthcare interoperability environment because it demonstrates the use of FHIR R4.0.1 in federal interoperability requirements.

However, it is important not to misrepresent its scope.

CMS-0057-F does not directly require every homecare agency to implement FHIR R4.0.1.

Its direct requirements apply to the specified payer organizations and other participants covered by the rule.

For a homecare agency, the practical relevance depends on its relationships and integrations with those organizations.

FHIR R5: newer does not automatically mean better

FHIR R5, version 5.0.0, was published on 26 March 2023.

It is a real, published release and includes further development of the FHIR specification.

However, it has Trial Use status.

That means its publication should not be confused with universal adoption across US healthcare systems.

The federal regulatory implementation specifications examined here remain based on R4.

ONC’s FHIR ecosystem guidance also identifies R4.0.1 as the appropriate version to continue using for new standards development and implementations unless a compelling use case requires functionality exclusive to R5.

For a homecare agency, this is a practical consideration.

Selecting a platform solely because it advertises support for the newest FHIR release does not guarantee compatibility with the hospitals, healthcare providers, or payer systems with which the agency needs to communicate.

The vendor should demonstrate compatibility with the actual integration partners and their supported specifications.

What about Epic and Oracle Health?

A buyer should avoid assuming that every major EHR vendor supports every FHIR version.

The specific product, API, endpoint, and integration arrangement matter.

Oracle Health’s publicly documented Millennium Platform API materials list R4 and older API offerings.

However, this does not establish that Oracle Health has no R5 support anywhere across its products or other integration arrangements.

Similarly, there is insufficient official evidence to make a blanket statement that Epic does not support R5.

The responsible approach is to verify the exact capabilities of the EHR and API involved in the proposed integration.

A software vendor should be able to identify the supported version rather than relying on assumptions about another company’s product portfolio.

FHIR R6: still in ballot

FHIR R6 is the next major release under development.

The official HL7 version documentation records its development milestones, including ballot 5 and snapshot 1 on 17 July 2026.

The September 2026 R6 snapshot describes the specification as undergoing a full ballot.

As of the November 2026 research period, R6 remains in ballot rather than being a published final release.

A firm final-publication date has not been confirmed by the official materials examined.

That means a buyer should not base a current procurement decision on a predicted R6 publication date.

The published US Core roadmap provides another important detail.

It identifies R6, rather than R5, as the next planned underlying FHIR version for US Core.

However, the roadmap does not establish a firm transition date.

It also does not provide a guaranteed period for continued R4 support after that transition.

An agency should therefore avoid assuming that R4 will remain supported for a particular number of years without obtaining confirmation from its software provider.

Why FHIR versions are not automatically interchangeable

FHIR versions can introduce changes to resource structures, data elements, terminology bindings, cardinalities, and API capabilities.

This means an R4 integration should not automatically be expected to work unchanged with an R5 server.

Consider appointment scheduling.

FHIR R5 includes more explicit support for recurring appointments through additional recurrence-related elements.

These include recurrence templates and information about frequency, time zones, and repeated appointment patterns.

R5 also introduces a more structured subscription framework.

The SubscriptionTopic resource defines the events or resource changes that clients can subscribe to, while Subscription describes the client’s subscription to a topic.

These developments demonstrate why version transitions can involve technical work.

However, this does not mean that every R4 resource is incompatible with every R5 server.

Compatibility depends on the resource, profile, implementation, server capabilities, and available conversion mechanisms.

For a homecare agency, the practical lesson is to treat a version transition as an interoperability project that needs evaluation and testing.

It should not be treated as a simple configuration change.

The FHIR version question every buyer should ask

When a vendor says its software is FHIR-ready, ask:

Which exact FHIR version and implementation guide does your system support?

A useful answer should identify:

The phrase FHIR-ready without a version number provides very little useful information.

A system might support a particular FHIR resource but not the implementation guide required by an integration partner.

It might support an API but not the particular interaction needed to exchange appointment or patient information.

A buyer needs to know what works, not simply what appears on a vendor’s feature list.

6. What to Ask a Vendor Before You Sign

A healthcare software demonstration can make a platform look straightforward.

The vendor may show patient profiles, appointment screens, care documentation, and administrative dashboards. These features are important, but they do not establish whether the system is appropriate for handling PHI.

Before signing an agreement, a homecare agency should ask specific questions about contractual responsibilities, technical safeguards, interoperability, and data access.

The following checklist provides a practical starting point. If you are still scoping what the first version of the platform should include, our guide to what an MVP is explains how to keep the first build focused.

1. Will you sign a Business Associate Agreement before receiving PHI?

This should be one of the first questions.

If a software provider qualifies as a business associate, the agency needs an appropriate written BAA before allowing that provider to handle PHI on its behalf.

This includes applicable cloud service providers that create, receive, maintain, or transmit ePHI.

Importantly, a cloud provider can qualify as a business associate even if it stores only encrypted patient information and does not possess the encryption key.

There is a narrow exception for qualifying conduit services that merely transmit information and have only transient access, but ordinary cloud storage and processing services generally cannot rely on that exception simply because their employees cannot read encrypted data.

Ask the vendor:

Do not move real patient information into a vendor’s system before the necessary BAA is signed.

A general statement that the vendor follows HIPAA principles is not a substitute for the required contractual arrangement.

2. Which encryption standards do you use?

Ask the vendor to explain how information is protected both when stored and when transmitted.

For procurement purposes, an agency can request:

These are technical procurement specifications, not a statement that HIPAA explicitly mandates each named algorithm or protocol.

The current Security Rule treats encryption as an addressable implementation specification.

Nevertheless, requiring clear encryption standards helps an agency assess how its vendor protects sensitive information.

Avoid accepting an answer such as “we use industry-standard encryption” without further explanation.

Ask which algorithms and protocols are used, where encryption applies, and how encryption keys are managed.

The agency should also understand whether the vendor’s arrangements cover the relevant production systems, backup environments, and data transfers.

3. Does every user have a unique login?

The software should identify individual users rather than relying on shared credentials.

Unique user identification is an express HIPAA technical safeguard requirement.

This matters because a healthcare agency needs to understand who accessed a patient’s information and which activities were performed.

If several employees use the same login, it becomes difficult to establish individual accountability.

Ask whether the platform supports:

MFA is a particularly useful security requirement to request.

Although it is not a general express requirement under the current Security Rule, it is included in the proposed 2025 modernization and provides an additional layer of protection.

4. Can access be restricted by role?

A homecare agency has different types of employees with different responsibilities.

Caregivers, nurses, administrators, billing staff, and management do not necessarily need identical access to patient information.

Ask whether the platform supports role-based access control (RBAC).

With RBAC, access permissions are associated with defined roles and responsibilities.

For example:

The specific permissions should reflect the agency’s operations and applicable HIPAA requirements.

Also ask whether administrators can modify permissions when an employee changes roles.

A good access-control approach should make it possible to restrict information without relying entirely on employees to decide which records they should open.

5. Does the system maintain audit logs?

Audit controls are required under the HIPAA Security Rule.

A vendor should be able to explain what activity is recorded and how authorized personnel can review it.

Useful audit information may include:

For procurement, an agency can also request immutable audit logs.

Immutability means that recorded information is protected against unauthorized alteration or deletion.

This is a stronger security specification, not an express HIPAA requirement by that name.

Ask whether audit records can be exported, how long they are retained, and which authorized personnel can review them.

The agency should also understand whether the vendor can provide relevant audit information when investigating a suspected security incident.

6. Does the system support automatic logoff and session timeouts?

Automatic logoff is an addressable implementation specification under the current Security Rule.

It is particularly relevant to homecare agencies because staff may access patient information from different devices and working environments.

A caregiver might finish documenting a visit and move on to another responsibility. If the application remains open, another person could potentially access the information.

Ask whether the platform:

The agency should understand how these controls work in real-world use.

A session timeout should support security without making authorized care documentation unnecessarily difficult.

7. Can the vendor provide information about its security risk analysis?

The agency should understand how security risks are identified, assessed, and managed.

Under the current Security Rule, risk analysis is an important administrative safeguard.

Ask the vendor:

The agency should not assume that a vendor’s risk analysis automatically satisfies the agency’s own HIPAA responsibilities.

The two organizations have different responsibilities and may face different risks.

However, understanding the vendor’s security practices is an important part of evaluating a business associate.

It is also useful to ask whether the vendor has written incident-response procedures and how it tests them.

These are areas highlighted by the proposed Security Rule modernization.

How a vendor tests and ships changes matters too — our beginner’s guide to DevOps for startups explains what disciplined testing and deployment looks like.

8. Which FHIR version and US Core implementation guide do you support?

Do not settle for a general answer that the software supports FHIR.

Ask the vendor to identify its actual implementation.

Relevant questions include:

If the vendor claims R5 support, ask which specific EHRs and APIs have been tested.

Likewise, if the vendor mentions R6, establish whether it is referring to a published standard or a development or ballot version.

The agency should not assume that a newer FHIR release automatically provides better interoperability with its existing healthcare partners.

R4.0.1 remains the evidence-backed baseline for many US interoperability specifications examined in this guide.

9. How does information move in and out of the system?

Data access should not become an afterthought.

An agency should understand how it can retrieve its information if it changes software providers or needs to transfer records to another authorized system.

Ask:

This is especially important for agencies that expect their technology needs to change over time.

A vendor should explain the data export process before the agency signs, not only when it decides to leave.

The ability to retrieve information in a usable format is an important part of maintaining operational continuity.

10. Can the vendor explain its security responsibilities in writing?

Finally, ask the vendor to explain which security responsibilities belong to the provider and which remain with the agency.

For example, the vendor may operate the hosting environment and provide technical access controls.

The agency remains responsible for its own workforce policies, authorized access decisions, and other applicable HIPAA obligations.

A written explanation should address relevant responsibilities, incident reporting, subcontractors, data handling, and contractual arrangements.

Avoid relying on informal assurances given during a demonstration.

Vague promises of “HIPAA compliance” without specific details are a red flag.

A vendor should be able to identify its safeguards, explain its BAA arrangements, specify its encryption practices, and state exactly which FHIR version it supports.

The more clearly these details are documented, the easier it is for an agency to evaluate whether the platform meets its operational and security requirements.

For larger or more complex platforms, our enterprise software development overview explains how bigger builds are structured.

7. Frequently Asked Questions

Does healthcare software need to be HIPAA compliant if it only stores patient information?

Yes, when the software is used by a covered entity or business associate in a way that involves protected health information, applicable HIPAA requirements must be considered. Storing patient information can itself involve maintaining PHI. A cloud or software provider that maintains ePHI on behalf of a covered entity can qualify as a business associate, even if it does not directly provide healthcare services or have access to the encryption keys. The agency should establish the appropriate BAA and evaluate the provider’s safeguards before allowing PHI to enter the system.

Does HIPAA require AES-256 encryption and multi-factor authentication?

Not as universal, specifically named requirements under the current Security Rule. Encryption is an addressable implementation specification under the current rule. Organizations must assess whether it is reasonable and appropriate and document their decisions. MFA is a strong security practice, but it is not a general express requirement under the existing Security Rule. Both encryption requirements and MFA appear in the proposed 2025 Security Rule modernization. A homecare agency can still request AES-256 encryption and MFA as procurement requirements when evaluating software providers.

Should a homecare agency choose FHIR R4 or R5?

For US healthcare integrations, FHIR R4.0.1 is the established baseline supported by the federal interoperability specifications examined in this guide. R5 is a published release, but it is not the version identified in the federal regulatory implementation specifications discussed here. The best choice depends on the systems the agency needs to connect with. A buyer should ask the vendor which version it supports, which US Core implementation guide it uses, and whether the specific integration has been tested. R6 is still in ballot, so it should not be treated as an already published final standard.

Is signing a Business Associate Agreement enough to make a software vendor HIPAA compliant?

No. A BAA is an important contractual requirement, but it does not independently establish that the vendor has implemented appropriate security safeguards. The agency should also assess access controls, authentication, audit controls, encryption, risk management, incident response, and other relevant security arrangements. The vendor should be able to explain its responsibilities and provide appropriate documentation. The agency also retains its own HIPAA responsibilities. It cannot transfer every compliance obligation to its software provider simply by signing an agreement.

Is this guide legal advice, and can an agency rely on it to determine its HIPAA obligations?

No. This post is general information, not legal advice. HIPAA requirements can depend on an organization’s activities, relationships, systems, and applicable circumstances. A homecare agency should confirm the details with a qualified healthcare compliance professional or attorney before relying on them when making legal, contractual, or regulatory decisions.

8. Discuss Your Healthcare Software Needs

Choosing healthcare software means looking beyond the features shown in a product demonstration. Your agency needs a system that supports appropriate patient-data protection, clear contractual responsibilities, reliable access controls, and interoperability with the healthcare organizations it works with. WebSphere Innovations approaches healthcare software development with a focus on building compliance considerations into the software from the beginning rather than treating them as an afterthought. If your agency is evaluating a new platform or planning a healthcare software project, discuss your requirements with the team. Visit contact us to discuss your healthcare software needs and the technical capabilities your organization wants to prioritize.

Leave a Reply

Your email address will not be published. Required fields are marked *