We used to have multiple relational schemas:
- a "basic" schema that puts all resource types into the same tables
- a "normalized" schema that uses a set of tables per resource type
At the implementation level, the normalized schema extends the basic schema, which makes things more complicated than they need to be. We never updated the "basic" schema for R4 and so this is needless complexity.
Acceptance criteria 1: Class hierarchy in fhir-persistence-jdbc should be simplified and without reference to the basic schema
Acceptance criteria 2: Configuration and documentation related to the "basic" schema should be removed
We used to have multiple relational schemas:
At the implementation level, the normalized schema extends the basic schema, which makes things more complicated than they need to be. We never updated the "basic" schema for R4 and so this is needless complexity.
Acceptance criteria 1: Class hierarchy in fhir-persistence-jdbc should be simplified and without reference to the basic schema
Acceptance criteria 2: Configuration and documentation related to the "basic" schema should be removed