stake holder meeting



This is a list of the current domain names in the FHIM model.

For a description of the individual domains, view the model, select the domain name and at the left click on Diagrams.

View the FHIM Fact Sheet

What is a domain?   In general a domain is a "sphere of knowledge, influence or activity".   Here in the FHIM, it is a subject area in healthcare which we model.  

According to Wikipedia: a Domain model in problem solving and software engineering can be thought of as a conceptual model of a domain of interest (often referred to as a problem domain) which describes the various entities, their attributes, roles and relationships, plus the constraints that govern the integrity of the model elements comprising that problem domain."

"The domain model also identifies the relationships among all the entities within the scope of the problem domain, and commonly identifies their attributes."

From: http://en.wikipedia.org/Wiki/Domain_model

Domain-driven design (DDD) is an approach to developing software for complex needs by deeply connecting the implementation to an evolving model of the core business concepts.[1] The premise of domain-driven design is the following:

  • Placing the project's primary focus on the core domain and domain logic
  • Basing complex designs on a model
  • Initiating a creative collaboration between technical and domain experts to iteratively cut ever closer to the conceptual heart of the problem.

Domain Driven Design is not a technology or a methodology. DDD provides a structure of practices and terminology for making design decisions that focus and accelerate software projects dealing with complicated domains.

The Domains of the Federal Health Information Model
FHIM Package Names
View the FHIM Model  
  1. Adverse Event Reporting
  2. Allergies
  3. Assessment (Questionnaires)
  4. Audiology and Speech Pathology
  5. Behavioral Health
  6. Blood Bank
  7. Care Plan
  8. Clinical Decision Support
  9. Clinical Document
  10. Clinical Observation
  11. Common Classes - these are classes used by multiple domains
  12. Common Product - medications, food products and devices
  13. Consultation
  14. Data Types contains classes used as data types through out the model. for example: Address, Point in Time, Person Name, or Telecommunications (phone number, email)
  15. Dental
  16. Detailed Clinical Models
  17. Dietetics
  18. Encounter
  19. Enrollment, Eligibility and Coordination of Benefits (COB)
  20. Health Concern
  21. Home-Based Primary Care
  22. Imaging
  23. Immunization
  24. Laboratory General and Lab Result Report to an EHR ( laboratory orders and result reporting)
  25. Medication Administration
  26. Oncology Registry
  27. Orders
  28. Patient Education
  29. Person Demographics
  30. Pharmacy
  31. Prosthetics
  32. Provider
  33. Public Health Reporting
  34. Security and Privacy
  35. Social Work
  36. Spinal Cord
  37. Surgery
  38. Vital Signs
  39. Woman's Health

For detailed descriptions of a domain, click View the FHIM model, then double click on the box for the desired domain. Also click on + Diagrams or on + Models at the upper left to see the drop down items. For example, the Laboratory domain description is shown below.

For detailed Domain descriptions, view the model, click on the domain, then click on Diagrams

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 ).  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.  

ChromosomesThe FHIMS is an information model rather than a data model.  Data models are meant to be implemented, whereas information models are higher level requirements specifications.  From Wikipedia: an information model "in software engineering is a representation of concepts, relationships, constraints, rules, and operations to specify data semantics for a chosen domain of discourse. It can provide sharable, stable, and organized structure of information requirements for the domain context"


Additional contributors to FHIMS.org are welcome. Anyone wishing to participate or contribute, please contact us .

| |  |
Template by: Templatesperfect.com