Using CQL With FHIR
2.0.0 - STU 2 International flag

Publication Build: This will be filled in by the publication tooling

Library: USCore Example Model Definition (Experimental)

Official URL: http://hl7.org/fhir/uv/cql/Library/USCoreExample-ModelInfo Version: 3.1.0
Standards status: Informative Computable Name: USCoreExample
Other Identifiers: http://example.org/fhir/cqf/modelinfo/us/Library/Identifier#USCoreExample (use: official, ), OID:2.16.840.1.113883.4.642.40.37.28.14

Example Model definition for USCore (v3.1.0) Model. This is an experimental resource only used as an example in this implementation guide. Official model information files for the latest versions of USCore are being balloted and published as part of USCore (version 8.0.0+). Prior versions of model information files for US Core are being published in the Common CQL Assets for FHIR (US-based) implementation guide.

This Library is defined to provide an example of how ModelInfo files can be packaged in FHIR Library resources for maintenance, distribution, and implementation purposes.

Title: USCore Example Model Definition
Id: USCoreExample-ModelInfo
Version: 3.1.0
Url: USCore Example Model Definition
Official

USCoreExample

urn:oid:2.16.840.1.113883.4.642.40.37.28.14

Experimental: true
Type:

system: http://terminology.hl7.org/CodeSystem/library-type

code: model-definition

Date: 2021-03-07
Publisher: HL7 International / Clinical Decision Support
Description:

Example Model definition for USCore (v3.1.0) Model. This is an experimental resource only used as an example in this implementation guide. Official model information files for the latest versions of USCore are being balloted and published as part of USCore (version 8.0.0+). Prior versions of model information files for US Core are being published in the Common CQL Assets for FHIR (US-based) implementation guide.

Jurisdiction: 001
Topic:
Purpose:

This Library is defined to provide an example of how ModelInfo files can be packaged in FHIR Library resources for maintenance, distribution, and implementation purposes.

Content: application/xml
Encoded data (248384 characters)