
FHIMS HOME |
|
| This content was generated from the model on 2/19/12 |
| |
|
| Next Refresh in March 2012 |
| |
|
| Understanding the FHIM: |
1 Its primary purpose is a foundation on which to build architecture. If we were speaking of the architecture of a building, then the FHIM is the common foundation. The individual Federal agencies still will create their own elevations and floor plans. FHIMS also gives healthcare IT Standards Development Organizations (SDOs) a common focus and frame of reference for planning purposes. |
2. This model describes the information at a level of detail that is precise enough for business or clinical experts, but does not include implementation-platform specific details |
3. Information which is common among partner agencies is defined in the FHIM - agencies would extend the FHIM with agency-specific requirements. |
4. One goal is that an implementation compliant with the FHIM would be compliant to - or be easily mapped to - the appropriate industry standard. |
| 5. A secondary goal is to use the FHIM to "harmonize" the various healthcare data standards themselves through agency participation directly in the SDOs. |
|
|
| |
 |
| |
| Additional contributors are welcome. Anyone wishing to participate or contribute, please see Contact Us. |
|
| |
| The Federal Health Information Model |
| Collaborating on MODELING |
What is the FHIM? |
| The FHIM is a model of healthcare data developed for the FHA partner agencies. The FHIM project seeks to develop a common Logical Information Model or Computationally Independent Model (CIM). |
Background on the FHIM: More
|
|
|
|
|
|
|
|
|
The FHIMS Program
The FHIMS program is intended to coordinate the efforts of the partner agencies with the development of Electronic Medical Records, information and terminology standards, including the coordination of agency efforts at relevant Standards Development Organizations (SDOs). This website was created for Healthcare IT professionals for collaborative purposes only and is subject to the terms of use. It is not an official government website for the FHIMS program. The FHIMS is an information model rather than a data model. Data models are meant to be implemented, whereas information models are higher level specifications. |
Models, Source Code & other Artifacts: We have set up a project space under the auspices of Open Health Tools (OHT). This allows us to use the version control system hosted by OHT. Please contact us for access. Teleconference is held every Friday at 2:30 p.m. Eastern Time. |
The Federal Health Information Model is a project under a larger program called Federal Health Interoperability Modeling and Standards (FHIMS), which is an initiative of the Federal Health Architecture (FHA). Briefly, the United States federal government has established a Federal Enterprise Architecture (FEA), which provides guidance to federal agencies on how they should develop their enterprise architectures. The methodology used by FEA, the Federal Segment Architecture Methodology (FSAM) recognizes that some "lines of businesses" in which the federal government is engaged cross agency boundaries. The healthcare line of business is one such case. As a result, the FHA was established as a partnership of over 20 departments and agencies to coordinate Healthcare Information Technology (sometimes called Healthcare IT, or HIT) activities among those partners. The FHA is managed by the Office of the National Coordinator for Health IT (ONC). The FHA has served as a forum by which the partner agencies have collaborated on several important initiatives, including the Nationwide Health Information Network.
The FHIMS program is intended to coordinate the efforts of the partner agencies with respect to information and terminology standards, including the coordination of agency efforts at relevant Standards Development Organizations (SDOs) such as Health Level Seven (HL7), the National Council for Prescription Drug Programs (NCPDP), Integrating the Healthcare Enterprise (IHE), and others. Many of the partner agencies are already active in some of these SDOs, in which case the FHIMS program can help agencies speak with a single voice at the SDOs while also reducing redundant participation. For those agencies that do not yet have a presence in a particular SDO, this program provides a mechanism for agencies to delegate issues to another agency. For example, if the Department of Veterans Affairs (VA) is active in the Organization for the Advancement of Structured Information Standards (OASIS), and the Indian Health Service (IHS) is not, the FHIMS program provides an opportunity for IHS to learn of relevant OASIS activities, and for IHS to request the VA representatives to OASIS to champion a particular issue.
Another FHIMS initiative is the Federal Health Terminology Model project, which coordinates partner agency efforts to develop healthcare terminology models (i.e., new content), and to enumerate "value sets" that can be associated with the Information Model. The Terminology Model is closely related to the Information Model, as they are each describing the same real-world concepts from two different angles. The Information Modeling team will work very closely with the Terminology Modeling team to identify those concepts which should be enumerated in a value set, to define that value set, and to define the members of the value set. |