Enhancements to Fhir Schema Converter #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. Now allows a tenant schema to be specified in application.conf. 2. The schema allows views to be generated are for that tenant schema (as opposed to the way it was before, where it expected the tables to exist in the public schema). 3. The view SQL also prefixes the view name and table name with the optional schema name. 4. It still applies the views to the database as it did before, but it now also writes each view to a views folder. 5. On this commit no columns are excluded from the views (but we may well re-instate the capability to do column filtering based on actual data in the tables)
…e in FHIR database (as an alternative to using a file).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added ability to configure a tenant schema on the database connection string, plus the ability to fetch the FHIR resource JSON schema from the StructureDefinition table.
Note: this latter not as useful as I thought it was going to be because the schema definition in the FHIR database is at a more summary level than the CareConnect schema file, so less fields than you would expect get exposed in the views.