AUCDI and implementations

The AUCDI does not need to be read or consumed as a whole single product. Sections can be used as necessary for specific use cases. This is true for both the data model and the recommended terminology value sets.

It is intended that AUCDI will continue to evolve to provide a foundation for future uses. For example, it will both inform and be incorporated into the eRequesting use case, and any new common data elements may also be added to AU Core if determined to be foundational, for example Pregnancy Status. When combined with eRequesting specific requirements, the result will be the eRequesting Data for Interoperability. All future projects will commence with the AUCDI at their core.