Domain Package Names
-
Domain Package Names
This is a list of the current domain names in the FHIM model. For a description of each domains, View the model, select the domain name and at the left click on Diagrams.
-
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."
-
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.
-
What is a domain?
In general a domain is a "sphere of knowledge, influence or activity". In the FHIM, it is a subject area in healthcare which we model.
-
The FHIMS is an information model rather than a data model. Data models are meant to be implemented as apps, 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."
-
Domain Driven Design
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. The premise of Domain Driven Design is placing the project's primary focus on the core domain and domain logic, basing complex designs on a model, and initiating a creative collaboration between technical and domain experts to iteratively cut ever closer to the conceptual heart of the problem. DDD 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.
FHIM Package Names
FHIM Package Names
This is a list of the current domain names in the FHIM model. For a description of each domain, view the model, select the domain name and click on diagrams on the left.
Adverse Event Reporting
Allergies
Assessment (Mental Health and all other)
Audiology and Speech Pathology
Behavioral Health
Blood Bank
Care Plan
Clinical Decision Support
Clinical Document
Clinical Observations
Common Product - these are classes used by multiple domains
Consultation
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)
Dental
Detailed Clinical Models
Dietetics
Encounter
Enrollment, Eligibility and Coordination of Benefits
Health Concern
Home-Based Primary Care
Imaging
Immunization
Laboratory General and Lab Result Report to an EHR -lab orders and result reporting
Medication Administration
Oncology Registry
Orders
Patient Education
Person Demographics
Pharmacy
Prosthetics
Provider
Public Health Reporting
Security and Privacy
Social Work
Spinal Cord
Surgery
Vital Signs
Woman's Health