Skip to content

Commit

Permalink
Merge pull request #92 from mzuhl/CQF-1068
Browse files Browse the repository at this point in the history
CQF-1068 - QM IG May Ballot- Apply Ballot Trackers #12
  • Loading branch information
brynrhodes committed Nov 22, 2021
2 parents 4db6f4b + ee8016e commit 6dac193
Show file tree
Hide file tree
Showing 9 changed files with 10,606 additions and 9,827 deletions.
348 changes: 348 additions & 0 deletions hs_err_pid20372.log

Large diffs are not rendered by default.

16 changes: 15 additions & 1 deletion input/pages/measure-conformance.md
Original file line number Diff line number Diff line change
Expand Up @@ -1457,4 +1457,18 @@ Refer to the [ConceptMap Resources section](terminology.html#conceptmap-resource
{:.new-content}
Member Attribution (ATR) lists are used between Payers and Providers for implementing risk-based contracts, value based contracts, care gap closures and quality reporting. Creation of a Member Attribution List typically starts with a need to identify the patients for a specific purpose such as Quality Reporting. The [CQFMQualityProgram](StructureDefinition-quality-program-cqfm.html) is a library profile used to establish a set of related quality improvement artifacts such as a measure program and can be used to establish a "release" of a quality program.

Referring to the [Member Attribution Lists Workflows and Definitions](http://build.fhir.org/ig/HL7/davinci-atr/usecases.html#member-attribution-list-workflows-and-definitions) within the Da Vinvi - Member Attribution (ATR) List IG, there is a potential in using "contract identifier" to look up a group but not prescriptive from the perspective of QM IG.
Referring to the [Member Attribution Lists Workflows and Defintions](http://build.fhir.org/ig/HL7/davinci-atr/usecases.html#member-attribution-list-workflows-and-definitions) within the Da Vinvi - Member Attribution (ATR) List IG, there is a potential in using "contract identifier" to look up a group but not prescriptive from the perspective of QM IG.


### Must Support

**Conformance Requirement 3.18 (Must Support Elements):** [<img src="conformance.png" width="20" class="self-link" height="20"/>](#conformance-requirement-3-18)
{: #conformance-requirement-3-18}
For resource instances claiming to conform to Quality Measure IG profiles, Must Support on any profile data element SHALL be interpreted as follows:

* Authoring systems and knowledge repositories SHALL be capable of populating all Must Support data elements.
* Evaluating systems SHALL be capable of processing resource instances containing Must Support data elements without generating an error or causing the evaluation to fail.
* In situations where information on a particular data element is not present and the reason for absence is unknown, authoring and repository systems SHALL NOT include the data elements in the resource instance.
* For example, for systems using '9999' to indicate unknown data values, do not include '9999' in the resource instance.
* When consuming resource instances, evaluating systems SHALL interpret missing data elements within resource instances as data not present for the artifact.
* Submitting and receiving systems using Quality Measure artifacts to perform data exchange or artifact evaluation operations SHALL respect the must support requirements of the profiles used by the artifact to describe the data involved in the operation.
106 changes: 106 additions & 0 deletions input/resources/Library-quality-program-cqlOptions-example.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,106 @@
{
"resourceType": "Library",
"id": "quality-program-cqloption-example",
"meta": {
"profile": [
"http://hl7.org/fhir/us/cqfmeasures/StructureDefinition/quality-program-cqfm"
]
},
"url": "http://hl7.org/fhir/us/cqfmeasures/Library/quality-program-cqloption-example",
"identifier": [
{
"use": "official",
"system": "http://example.org/fhir/cqi/ecqm/Library/Identifier",
"value": "QualityProgramCQLOptionExample"
}
],
"version": "0.1.0",
"name": "QualityProgramCQLOptionExample",
"title": "Quality Program CQL Option Example",
"status": "active",
"experimental": true,
"type": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/library-type",
"code": "asset-collection"
}
]
},
"date": "2019-09-03",
"publisher": "Health Level 7 International - Clinical Quality Information Work Group",
"contact": [
{
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/cqi/index.cfm"
}
]
}
],
"jurisdiction": [{
"coding": [{
"system": "urn:iso:std:iso:3166",
"code": "US"
}]
}],
"description": "This library is an example of a quality program with cqlOptions extension.",
"approvalDate": "2019-08-03",
"lastReviewDate": "2019-08-03",
"useContext": [
{
"code": {
"system": "http://terminology.hl7.org/CodeSystem/usage-context-type",
"code": "program"
},
"valueCodeableConcept": {
"coding": [
{
"system": "http://hl7.org/fhir/us/cqfmeasures/CodeSystem/quality-programs",
"code": "ep-ec",
"display": "EP/EC"
}
]
}
}
],
"relatedArtifact": [
{
"extension": [
{
"url": "http://hl7.org/fhir/us/cqfmeasures/StructureDefinition/cqfm-programIdentifier",
"valueIdentifier": {
"value": "EXM123"
}
},
{
"url": "http://hl7.org/fhir/us/cqfmeasures/StructureDefinition/cqfm-qualityDomain",
"valueCodeableConcept": {
"text": "Example Quality Domain"
}
},
{
"url": "http://hl7.org/fhir/us/cqfmeasures/StructureDefinition/cqfm-meaningfulMeasureArea",
"valueCodeableConcept": {
"text": "Example Meaningful Measure Area"
}
}
],
"type": "composed-of",
"resource": "http://hl7.org/fhir/us/cqfmeasures/Measure/measure-exm",
"display": "Example Measure"
},
{
"extension": [
{
"url": "http://hl7.org/fhir/us/cqfmeasures/StructureDefinition/cqfm-cqlOptions",
"valueCqfmCqlOptions": "Example CQL Options"
}
],
"type": "composed-of",
"resource": "http://hl7.org/fhir/us/cqfmeasures/2021May/Library-EXMComputableLibrary.html",
"display": "Example Computable library"
}
]
}
Loading

0 comments on commit 6dac193

Please sign in to comment.