This wiki has undergone a migration to Confluence found Here
RIMBAA: California SIIS
Jump to navigation
Jump to search
This page uses terminology as defined in this whitepaper.
Created a RIM-based relational database structure to persist the data content of immunization related messages used in the California Statewide Immunization Information System (SIIS) System Integration Project (SIP)
The information needs of the SIIS SIP immunization database are documented.
- The information needs are mapped to a v3 R-MIM. Perform the usual localization activities, e.g. constrain cardinalities, data types (through demotion), and coding systems.
- A relevant subset of the RIM classes is determined - based on the classCodes as present in the R-MIM. Attributes that aren't used by any given clone of one particular classCode in the R-MIM are removed from the "RIM subset" created by step 1.
- Optimize the inheritance hierarchies, e.g. by means of propagation of parent associations/attributes to child classes, or by promotion of child attributes to the parent class.
- Promote collection attributes (SET,LIST,BAG) to separate classes.
- Create 1 database table per resulting class. Add relationships between tables. Define data integrity rules (based on LDM requirements; based on requirements by the HL7 standard). Determine (primary) keys, and where these should be used as foreign keys.
In terms of the Technology Matrix all of the above is the RR square. The method used for the SIIS/SIP project probably results in a almost optimal database definition - fit for purpose.
Source: AMS
