This profile is based on HL7 EHR-S FM, Release 1, February 2007. Key to the FM and derived profiles is the concept of conformance which may be defined as verification that an implementation faithfully meets the requirements of a standard or specification. A profile can be said to conform to the FM if it adheres to the defined rules identified by the FM specification. The LTC-NH EHR-S Functional Profile adheres to the defined rules of the EHR-S FM. Similarly, an EHR-S may claim conformance to the LTC-NH EHR-S Functional Profile if it meets all the requirements outlined in this profile.
5.2. Functional Priorities
The LTC-NH EHR-S Functional Profile Workgroup recognizes that clinical computing is an evolving field, and that many of the desired functions of EHR systems are not currently available. Nevertheless, it is important for functional profiles to outline major trends and articulate a vision for functionality (especially interoperability) for the future. Furthermore, the delineation of potential functions for future implementation and adoption should guide vendors in system development, and help purchasers develop and articulate to vendors a strategic vision for future functional requirements.
Each function in the profile is assigned a single priority as follows:
||Indicates that the implementation of the function is mandatory and SHALL be implemented in EHR systems claiming conformance to this profile.
||Indicates that the function has significant importance but is not widely available. The function will become mandatory and SHALL be implemented in EHR systems claiming conformance to this profile by the end of the year identified.
||Indicates that, while the function may have value to some organizations, it is not viewed as being essential.
||Function not applicable in the nursing home setting and rejected for purposes of the LTC-NH EHR-S Functional Profile.
5.3. Normative Language
The key words SHALL, SHALL NOT, SHOULD, and MAY in this document are to be interpreted as described in HL7 EHR-S Functional Model, Release 1, February 2007 Chapter 2: Conformance Clause:
||Indicates a mandatory requirement to be followed (implemented) in order to conform. Synonymous with "is required to" and "must".
||Indicates a prohibited action. Synonymous with "prohibited" and "must not".
||Indicates an optional recommended action, one that is particularly suitable, without mentioning or excluding others. Synonymous with "is permitted and recommended".
||Indicates an optional, permissible action. Synonymous with "is permitted".