The implementation process retrieves information and terminology content from the FHIM model and generates draft implementation standards and other implementation artifacts such as FHIR profiles and CCDA templates, implementation guides, and APIs for conformance testing of an implementation against the requirements of an implementation standard.
Implementation content consists of UML templates and implementation detailed clinical model structure definition specifications to support generating, conformance testing, and validating FHIR, CCDA, V2, or other implementation paradigm artifacts. This applies to an organization’s data exchange APIs, an organization’s information exchange requirements, requirements traceability, and the applicable implementation-paradigm standard.
The implementation architecture consists of an open source software application called Model Driven Health Tools (MDHT) and a standard called Model Driven Message Interoperability (MDMI). MDHT uses FHIM UML templates and structure definition specifications for processing FHIM information and terminology content into target implementation specifications, such as HL7 FHIR, CCDA, and V2.
FHIM Profile Builder
The profile builder process starts with editing FHIM domain classes, e.g., immunization, or existing FHIM templates using the profile editor component. The editing process produces new FHIM templates, that are stored in the FHIM repository. The templates are passed to the profile generator, which transforms them into implementation artifacts, e.g., FHIR profiles.
Profile builder content consists of information content from the FHIM and implementation structure definition content from Model Driven Health Tools. The profile editor component constrains or extends FHIM content and generates new content in the form of FHIM templates.
The profile builder architecture consists of two components - the profile editor and the profile generator - which connect via a cloud-based platform, interact via APIs, and store information in the FHIM repository. The profile editor retrieves and stores information using API calls. The profile generator produces FHIR profiles and other implementation artifacts.