HITSP Harmonization Framework

The HITSP Harmonization Framework defines a set of artifacts, known as "constructs", that:

• specify how to integrate and constrain selected standards to meet the business needs of a Use Case; and
• define a Roadmap to use emerging standards and to harmonize overlapping standards when resolved.

HITSP construct types, in decreasing breadth of scope, include:

• Interoperability Specifications
  Integration of all constructs used to meet the business needs of a Use Case
• Transaction packages
  Logical grouping of transactions
• Transactions
  Logical grouping of actions that use components and/or composite standards to realize the actions
• Components
  Logical grouping of base standards that work together, such as message and terminology

Specific rules exist for each construct type, defining what the construct type can be used for and how the construct types can be nested. Each construct:

• may contain construct types that are less inclusive in scope;
• may constrain any construct or standard it contains;
• may be constrained by any construct that contains it;
• is a candidate for reuse and repurposing, if a new set of requirements and context can be fulfilled by the construct without impacting existing uses of the construct;
• is uniquely identified and version controlled.