FHIM::FHIM Overview Diagram Diagram FHIM Overview Diagram The FHIM is organized into information "domains", which are simply logical groupings of related concepts. These domains are represented in the model by using UML Packages. It is important to note that every element in the model can "see" every other element in the model – the packages serve as convenient containers for groups of elements, not barriers. Therefore, domain diagrams can and do routinely include classes from other parts of the model. In order to explicitly indicate when a class from another package is being referenced, the class will be annotated with the owning package name.The FHIM was initially populated using existing models contributed by the partner agencies, including the VHA Health Information Model (VHIM), the Biomedical Research Integrated Domain Group (BRIDG) Model, the Common Product Model (CPM), the Integrated Case Safety Report (ICSR), and various other models developed by the partner agencies directly at HL7. Since the VHIM was the most comprehensive model, it was used as the starting point, with the FHIM modeling style applied. Then each domain is refined by teams comprised of subject matter experts from both the federal partner organizations and industry. Therefore, the FHIM contains domains that are in various states of completion, ranging from not started (aside from the initial application of the FHIM modeling style to the VHIM content) to in-progress to completed.This diagram is the main diagram of the FHIM, and it simply shows the UML packages which make up the FHIM. The packages are color-coded to indicate the current state of completion. Packages which are unchanged from the federal partner-supplied models are gray, packages which are in-progress are purple, and completed packages are green. Note that the packages marked in-progress may either be undergoing UML modeling or have completed the UML modeling phase but are awaiting or undergoing the Terminology modeling phase.FHIM data elements use simple or primitive datatypes wherever possible, but the FHIM does define several common structures for complex yet common cases (e.g, Address). See the Datatypes package for details on these.
