When creating a new schema for R4B, the update schema still warns of tables that should not be used.

[d0roppe]

Is your feature request related to a problem? Please describe. We should not create the tables that we don't want used when creating a new schema with R4B code.

Describe the solution you'd like when we update a new created schema for R4B we should not create tables and then warn not to use them. Here is an example of some of the messages in question.

2022-08-09 07:36:52.854 00000001 WARNING forhealth.fhir.schema.app.Main EffectEvidenceSynthesis tables [EffectEvidenceSynthesis_DATE_VALUES, EffectEvidenceSynthesis_LATLNG_VALUES, EffectEvidenceSynthesis_LOGICAL_RESOURCES, EffectEvidenceSynthesis_NUMBER_VALUES, EffectEvidenceSynthesis_QUANTITY_VALUES, EffectEvidenceSynthesis_RESOURCE_TOKEN_REFS, EffectEvidenceSynthesis_RESOURCES, EffectEvidenceSynthesis_STR_VALUES] will be dropped in a future release. No data should be written to these tables. If any data exists in these tables, that data should be exported (if desired) and deleted from these tables.
2022-08-09 07:36:52.854 00000001 WARNING forhealth.fhir.schema.app.Main MedicinalProduct tables [MedicinalProduct_DATE_VALUES, MedicinalProduct_LATLNG_VALUES, MedicinalProduct_LOGICAL_RESOURCES, MedicinalProduct_NUMBER_VALUES, MedicinalProduct_QUANTITY_VALUES, MedicinalProduct_RESOURCE_TOKEN_REFS, MedicinalProduct_RESOURCES, MedicinalProduct_STR_VALUES] will be dropped in a future release. No data should be written to these tables. If any data exists in these tables, that data should be exported (if desired) and deleted from these tables.
2022-08-09 07:36:52.854 00000001 WARNING forhealth.fhir.schema.app.Main MedicinalProductAuthorization tables [MedicinalProductAuthorization_DATE_VALUES, MedicinalProductAuthorization_LATLNG_VALUES, MedicinalProductAuthorization_LOGICAL_RESOURCES, MedicinalProductAuthorization_NUMBER_VALUES, MedicinalProductAuthorization_QUANTITY_VALUES, MedicinalProductAuthorization_RESOURCE_TOKEN_REFS, MedicinalProductAuthorization_RESOURCES, MedicinalProductAuthorization_STR_VALUES] will be dropped in a future release. No data should be written to these tables. If any data exists in these tables, that data should be exported (if desired) and deleted from these tables.
2022-08-09 07:36:52.854 00000001 WARNING forhealth.fhir.schema.app.Main MedicinalProductContraindication tables [MedicinalProductContraindication_DATE_VALUES, MedicinalProductContraindication_LATLNG_VALUES, MedicinalProductContraindication_LOGICAL_RESOURCES, MedicinalProductContraindication_NUMBER_VALUES, MedicinalProductContraindication_QUANTITY_VALUES, MedicinalProductContraindication_RESOURCE_TOKEN_REFS, MedicinalProductContraindication_RESOURCES, MedicinalProductContraindication_STR_VALUES] will be dropped in a future release. No data should be written to these tables. If any data exists in these tables, that data should be exported (if desired) and deleted from these tables.
2022-08-09 07:36:52.855 00000001 WARNING forhealth.fhir.schema.app.Main MedicinalProductIndication tables [MedicinalProductIndication_DATE_VALUES, MedicinalProductIndication_LATLNG_VALUES, MedicinalProductIndication_LOGICAL_RESOURCES, MedicinalProductIndication_NUMBER_VALUES, MedicinalProductIndication_QUANTITY_VALUES, MedicinalProductIndication_RESOURCE_TOKEN_REFS, MedicinalProductIndication_RESOURCES, MedicinalProductIndication_STR_VALUES] will be dropped in a future release. No data should be written to these tables. If any data exists in these tables, that data should be exported (if desired) and deleted from these tables.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Acceptance Criteria

when creating a new schema and then updating the schema, we should not be warned about tables that were created but are asked not to use.

Additional context Add any other context or screenshots about the feature request here.