Skip to content

Latest commit

 

History

History
88 lines (57 loc) · 4.41 KB

README.md

File metadata and controls

88 lines (57 loc) · 4.41 KB
Raw

cqf-tooling

Maven Central Build Status project chat

Tooling for CQL and IG Authors

This tooling provides various useful tools for building CQFramework related content and implementation guides, including QUICK page generation, ModelInfo generation from StructureDefinitions, and ValueSet creation.

Usage

Building this project requires Java 11+ and Maven 3.8+. The resulting jar is compatible with Java 11+.

Build the project with:

mvn package

Run a specific operation using (example running VSAC Spreadsheet conversion):

mvn exec:java \
-Dexec.mainClass="org.opencds.cqf.tooling.cli.Main" \
-Dexec.args="-VsacXlsxToValueSetBatch \
-ptsd=src/test/resources/org/opencds/cqf/tooling/terminology \
-op=target/test/resources/org/opencds/cqf/tooling/terminology/output \
-setname=true \
-vssrc=cms"

Executable jars are produced by the CI system on Maven Central: Download executable jar

This can be run with java -jar tooling-cli-2.0.0.jar -VsacXlsxToValueSetBatch

Documentation of the various operations is provided in the Main class.

Commit Policy

All new development takes place on <feature> branches off master. Once feature development on the branch is complete, the feature branch is submitted to master as a PR. The PR is reviewed by maintainers and regression testing by the CI build occurs.

Changes to the master branch must be done through an approved PR. Delete branches after merging to keep the repository clean.

Merges to master trigger a deployment to the Maven Snapshots repositories. Once ready for a release, the master branch is updated with the correct version number and is tagged. Tags trigger a full release to Maven Central and a corresponding release to Github. Releases SHALL NOT have a SNAPSHOT version, nor any SNAPSHOT dependencies.

Release Process

To release a new version of the tooling:

  1. Update master to be a release version (and all the reviews, bug fixes, etc. that that requires)
    1. Regression test against IGs known to use CQF Tooling
  2. Passed Travis Build = ready for release
  3. Create a Github Release (which creates a tag at the current commit of master)
    1. Choose the "Auto-generate release notes" option
  4. Travis does the release to Maven
    1. Ensure binaries are published to https://oss.sonatype.org/#view-repositories;public~browsestorage~org/opencds/cqf/tooling
  5. Update master to vNext-SNAPSHOT
  6. Close all issues included in the release

Getting Help

Bugs and feature requests can be filed with Github Issues.

The implementers are active on the official FHIR Zulip chat for CQL.

Inquires for commercial support can be directed to info@alphora.com.

Related Projects

Clinical Quality Language - Tooling in support of the CQL specification, including the CQL verifier/translator used in this project.

CQL Support for Atom - Open source CQL IDE with syntax highlighting, linting, and local CQL evaluation.

CQF Ruler - Integrates this project into the HAPI FHIR server, exposing some functionality as services.

License

Copyright 2019+ Dynamic Content Group, LLC (dba Alphora)

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.