Execute a SQLQuery Library against ViewDefinition tables.

Export a view definition. User can provide view definition references and/or resources as part of the input parameters.

Execute a view definition against supplied or server data.

A profile for View Definitions intended to be shared between multiple systems. This requires that the View Definition have a defined URL and name. It also requires declaration of the FHIR version that the view is intended to be executed over, and the FHIR type of each column. This ensures consistent interpretation of the view across different view runner implementations.

A profile for View Definitions where each resulting field must contain only a simple scalar value. This is sometimes referred to as ‘CSV Mode’, but applies to any system that explicitly constrains its views or tables to tabular data.

A ViewDefinition represents a tabular projection of a FHIR resource, where the columns and inclusion criteria are defined by FHIRPath expressions.

The SQLQuery profile represents a SQL query that runs against ViewDefinition tables. It bundles the SQL, dependencies, and parameters for sharing and versioning.

Plain-text SQL query for human readability. Supplements the base64-encoded Attachment.data.

ValueSet of all codes from SQL Content Type Codes codesystem

ValueSet of all codes from Export Status Codes codesystem

ValueSet of all codes from Output Format Codes codesystem

Export status codes for SQL on FHIR.

Output format codes for SQL on FHIR.

Permitted contentType values for SQLQuery attachments, including dialect-specific variants.

Library types for SQL on FHIR.

Annotated SQL query example demonstrating how tooling can derive Library metadata.

A simple view for flattening a Condition resource. Some of the more commonly used fields are included in this flat view. A notable point is flattening of category.coding fields with one forEach construct as FHIRPath will take care of handling of nested arrays.

A simple view for flattening an Encounter resource. Some of the more commonly used fields are included in this flat view. Note this is valid for an R4 Encounter resource but not R5 (hence the fhirVersion).

Disambiguates OMOP and FHIR Patient views and joins diagnoses for context.

An example of unnesting patient addresses into multiple rows.

This view uses forEach to indicate we are unrolling these into separate rows. The join function is used to create a single address line.

An example of unnesting patient addresses and contact addresss into multiple rows, which are unioned together into a single table.

A minimal example of a patient demographics view. This view uses the first ‘official’ patient name for our demographics table.

An example demonstrating the use of %rowIndex to capture the position of elements within a collection. This is useful for preserving FHIR ordering semantics and creating surrogate keys that combine resource ID with element position.

Creates the same view as the ‘PatientDemographics’ example, but applies both the ShareableViewDefinition and TabularViewDefinition profiles.

A SQL query that retrieves the most recent address per patient with a city filter.

A simple view of blood pressure observations, with separate columns for systolic and diastolic values.