diff --git a/LICENSE b/LICENSE new file mode 100644 index 000000000..23ecd91af --- /dev/null +++ b/LICENSE @@ -0,0 +1,201 @@ +Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "{}" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright 2014-2018 The MITRE Corporation + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. diff --git a/OVERVIEW.md b/OVERVIEW.md index 0bcc37d58..8accf73e8 100644 --- a/OVERVIEW.md +++ b/OVERVIEW.md @@ -1,9 +1,9 @@ CQL Execution Framework Reference Implementation ================================================ -The reference implementation for executing CQL is currently under development. The reference implementation is intended to be used in CQF pilots and eventually integrated into production eCQM tools such as Bonnie and Cypress. +The reference implementation for executing CQL is currently under development. The reference implementation is intended to be used in CQF pilots and integrated into production eCQM tools such as Bonnie and Cypress. -The CQL execution framework is licensed under the open source [Apache Version 2.0](../../../LICENSE) license, and available as part of the [clinical_quality_language](https://github.com/cqframework/clinical_quality_language) project on GitHub. +The CQL execution framework is licensed under the open source [Apache Version 2.0](../../../LICENSE) license. Technologies ------------ @@ -19,7 +19,7 @@ Approach ### JSON ELM -Despite its name, the CQL execution framework does not execute CQL directly. Instead, it executes a JSON representation of the ELM. The [cql-to-elm](../../java/cql-to-elm) project is a reference implementation for translating CQL to ELM in XML or JSON. +Despite its name, the CQL execution framework does not execute CQL directly. Instead, it executes a JSON representation of the ELM. The [cql-to-elm](https://github.com/cqframework/clinical_quality_language/tree/master/Src/java/cql-to-elm) project is a reference implementation for translating CQL to ELM in XML or JSON. Consider the following CQL: @@ -124,4 +124,4 @@ Besides the `exec(patient_source)` method, the Executor class contains a couple Current Status -------------- -The CQL execution framework is still evolving and is not yet complete. The patient API, code service API, and format of results are likely to change quite a bit as implementation matures. In addition, there are still CQL/ELM operators not yet implemented in the execution framework. +The CQL execution framework is still evolving and is not yet complete. The patient API, code service API, and format of results may change as implementation matures. In addition, there may be CQL/ELM operators not yet implemented in the execution framework. diff --git a/README.md b/README.md index 73652eade..47ed0cd4a 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,7 @@ # CQL Execution Framework The CQL Execution Framework is a set of [CoffeeScript](http://coffeescript.org/) libraries that -can execute CQL artifacts expressed as JSON ELM. At this point, only a small subset of -functionality has been implemented (and a very simple JSON-based patient format is used). +can execute CQL artifacts expressed as JSON ELM. For more information, see the [CQL Execution Framework Overview](OVERVIEW.md). @@ -11,8 +10,9 @@ For more information, see the [CQL Execution Framework Overview](OVERVIEW.md). To use this project, you should perform the following steps: 1. Install [Node.js](http://nodejs.org/) -2. Install [CoffeeScript](http://coffeescript.org/) -3. Execute the following from the _cql-execution_ directory: `npm install` +2. Install [Yarn](https://yarnpkg.com) +3. Install [CoffeeScript](http://coffeescript.org/) +4. Execute the following from the root directory: `yarn install` # To Execute Your CQL @@ -24,11 +24,12 @@ There are several steps involved to execture CQL. First, you must create a JSON For easiest integration, we will generate a coffee file using cql-to-elm: 1. Install the [Java 8 SDK](http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html) -2. `cd ${branch}/Src/java` (replacing `${branch}` with the path to your git branch) +2. Clone the [clinical_quality_language](https://github.com/cqframework/clinical_quality_language) repository to a location of your choice +2. `cd ${path_to_clinical_quality_language}/Src/java` (replacing `${path_to_clinical_quality_language}` with the path to the local clone) 3. `./gradlew :cql-to-elm:installDist` -4. `./cql-to-elm/build/install/cql-to-elm/bin/cql-to-elm --format=COFFEE --input ${path_to_cql} --output ${branch}/Src/coffeescript/cql-execution/src/` +4. `./cql-to-elm/build/install/cql-to-elm/bin/cql-to-elm --format=COFFEE --input ${path_to_cql} --output ${path_to_cql-execution}/src/` -The above example put the example CQL into the coffeescript src directory to make things easy, but it +The above example puts the example CQL into the src directory to make things easy, but it doesn't _have_ to go there. If you put it elsewhere, you'll need to compile it to javascript and modify the examples below with the new path (where applicable). @@ -51,7 +52,7 @@ define InDemographic: Next, create a coffeescript file to execute the measure. This file will need to contain (or `require`) JSON patient representations for testing as well. Since our example CQL uses the QUICK data model, each patient is represented using a FHIR bundle. For ease of use, let's put the file -in the `coffeescript/cql-execution/src` directory: +in the `src` directory: ```coffee cql = require './cql' @@ -109,22 +110,22 @@ In the above file, we've assumed the JSON ELM coffeescript file for the measure also assumed a couple of very simple patients. Let's call the file we just created `age-exec.coffee`. -Now we must compile it to javascript in the `${branch}/Src/coffeescript/cql-execution/lib` -directory. There is a simple Cakefile build script for this (cake is installed with coffeescript): +Now we must compile it to javascript in the `lib` directory. There is a simple Cakefile +build script for this (cake is installed with coffeescript): -1. `cd ${build}/Src/coffeescript/cql-execution` +1. `cd ${path_to_cql-execution}` 2. `cake build` Now we can execute the measure using Node.js: -1. `cd ${build}/Src/coffeescript/cql-execution/lib` +1. `cd ${path_to_cql-execution}/lib` 2. `node age-exec` If all is well, it should print the result object to standard out. # To Run the CQL Execution Unit Tests -Execute `npm test` or `cake test`. +Execute `yarn test` or `cake test`. # To Develop Tests