Skip to content

Discussion Request: Handling External model(access,fhir,etc) tables that don't require harmonizaton. #36

@brendagutman

Description

@brendagutman

Is your feature request related to a problem? Please describe

Strategy for external models that don't need harmonization.

External models may have tables that will not require developer harmonization. We can take these tables out of all stb, and combined stages. Lookup tables can be ingested into the warehouse and read into dbt via the sources.yml. We would use dbt-model materialized=views within our access stage.

For example AccessDM.concept. This table could be created one time, and fit the exact needs of the access model.
We would create views in the access model stage so that the date are available within the access schema created for any of the environments.

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions