Developers are free to create new data store schema for use with their Universal Access screening and intake IEG2 scripts. There are, however, some constraints on the format of these schema. In some cases, requirements dictate that clients can screen for a program and then follow that screening with an application for benefits. In many cases such applications will be processed by Cúram and mapped to Cúram cases and evidence using the Cúram Data Mapping Engine (CDME). In these circumstances, it is advisable to use the CitizenPortal.xsd as a basis for the schema for screening, this is because the same data store schema must also be used for intake. In particular, the CDME features will not work correctly if schema are used that remove or change the data type of any of the attributes or entities in the CitizenPortal.xsd schema.
All schema that follow the pattern of the CitizenPortal.xsd schema are guaranteed to be safe for future upgrades; i.e., later releases. This means that upgrades will not add any new mandatory attributes or entities or change any existing attributes or entities that are currently required to support existing Cúram data mapping engine functionality.