Warning: A non-numeric value encountered in __TwigTemplate_1d6175267c2b7ae36f76c1eaf4e41a6422291b17b11b737c9f2083803f8a9118->doDisplay() (line 68 of sites/default/files/php/twig/6307747b12d35_page.html.twig_dD_n8l-WWepsbwOZDFS2ew6nL/aARTrsj72PY_xZYGUsLCQ5RxK8KN3oADBjQcmzzOWv8.php).
Implementation content is derived from the FHIM. The content generated by the implementation work stream is UML models and profiles defining FHIM templates, implementation guides, and APIs. An example of a UML model and profile (as displayed by the MDHT software) can be seen below. The UML model defines the structural representation of the FHIM template expressed as a target implementation (e.g., CDA , FHIR, etc.) and the corresponding UML profile defining required metadata to support the target platform. UML profiles are used for multiple purposes:
To bind UML structures to value set information
To define constraints properties (CDA severity level and rule id)
The foundational information in the FHIM is constrained to create data structures and semantics for a specific implementation.