HL7 EHR-S Functional Profile Codes – 7 January 2004

Definition

A Functional Profile is a specification which uses the EHR-S Functional Model to indicate which functions are required or implemented for certain implementations or Healthcare Delivery Settings.

Functional Profiles apply the standardized functions in the DSTU either to Healthcare Delivery Settings or to specific EHR-S implementations.

From that stand-point, Functional Profiles are divided into two categories:

  1. Constrainable Profiles
  2. Implementable Profiles

Constrainable Functional Profiles

Constrainable Profiles: These profiles use the HL7 EHR-S Functional Model to specify how functions are prioritized depending on the Healthcare Delivery Setting. The first step in defining a new Constrainable Functional Profile is to specify the supported Healthcare Delivery Settings. Additional Healthcare Delivery Settings may be added to a Constrainable Profile over time.

Once the Healthcare Delivery Settings are identified, each function in the EHR-S Functional Model is assigned a Priority. The set of priorities supported by Constrainable Functional Profiles differs from the set supported in the context of an Implementable Functional Profile.

Fig. 3: Constrainable Functional Profile (for a Realm)

Priority Options for Constrainable Functional Profiles

The possible priorities assigned to a function in a specific Healthcare Delivery Setting may be:

Option / Description / Code
Essential / This option indicates that the function must be feasible to implement now or within 18 months, meaning the function is readily available and the users can implement it. The function must also be critical or key to helping an EHR system address at least one of the following criteria [2]:
1.  Support Delivery of Effective Healthcare
2.  Improve Patient Safety
3.  Facilitate management of chronic conditions
4.  Improve efficiency
5.  Facilitate self-health management / E
Essential Future / The function should be feasible to implement by users and readily available in the future. The function must be also be critical or key to helping an EHR system address at least one of the following criteria [2]:
1.  Support Delivery of Effective Healthcare
2.  Improve Patient Safety
3.  Facilitate management of chronic conditions
4.  Improve efficiency
5.  Facilitate self-health management / EF
Optional / A level of significance applied to functions in relation to a functional profile. For the average users, the function is deemed an important/desirable but not a critical/key/essential component to an EHR system. It is recognized that for more complex healthcare provider settings, many items deemed optional may be viewed essential to them. / O
Not applicable/supported / A level of significance applied to functions in relation to a functional profile. The function is deemed an unsuitable component for an EHR system, in relation to a specific functional profile. / X

Implementable Functional Profiles

These profiles describe what EHR-S functions are fulfilled by a vendor applications or systems of applications in a healthcare enterprise. These profiles represent constraints assigned to a specific Healthcare Delivery Setting.

Priority Options for Implementable Functional Profiles

The possible priorities assigned to a function in a specific Healthcare Delivery Setting may be:

Option / Description / Code
Required / For applications: This means the application implements this function.
For healthcare and regulatory institution: This option means that the institution requires this function in the given setting. / R
Not Supported / This option indicates that the function is not supported or required in the current setting. / X
Example: Application-specific Implementable Functional Profile

In order to describe the capabilities of an application, we need to identify the realm in which the application is intended to be used. For instance, for an application to be used within the US, the starting point is the US-Realm Constrainable Functional Profile.

Step1: Identify Functions and Settings supported by Application B in US Realm

After that, the unsupported delivery settings are removed and the implemented functions are indicated with as “Required”.

Fig. 2: In the supported Healthcare Delivery Settings, mark the implemented functions

References

[1] HL7 EHR-System Functional Model – Draft Standard for Trial Use

[2] IOM Report on Private Safety….

Page 1 of 4