Giter Club home page Giter Club logo

gk-fhir-ig's Introduction

GATEKEEPER FHIR Implementation Guide

code: gk-fhir-ig

Test FHIR IG using Dockerfile

Build the image using docker build -t gk-fhir-ig ./. After the image has been built, use docker run -p 80:80 gk-fhir-ig to start the web server container which provides the static GATEKEEPER FHIR IG content under http://localhost.

gk-fhir-ig's People

Contributors

gcangioli avatar otiliakocsis avatar msusky avatar oreinecke avatar

Watchers

James Cloos avatar  avatar  avatar

gk-fhir-ig's Issues

Unable to build

When cloning this repository and then running 'docker build -t gk-fhir-ig ./', I get the following error:

executor failed running [/bin/sh -c wget -q https://github.com/HL7/fhir-ig-publisher/releases/latest/download/publisher.jar && java -jar publisher.jar -ig .]: exit code: 1

Can you guess why? How can I fix it?
Many thanks

Issues with whitespace using SUSHI 2.0

Background: SUSHI 2.0 implements several major features that will be balloted as part of FHIR Shorthand (FSH) STU2. One such feature, indented rules, interprets whitespace before rule markers (*) as an indicator of path context. Prior to SUSHI 2.0 and FSH STU2, whitespace before rule markers was insignificant.

Problem: This project contains FSH rules that have whitespace before the rule marker (*) and/or FSH keywords (e.g., Profile:, Parent:, etc.) that have whitespace before the first character. When SUSHI 2.0 processes these definitions, it attempts to determine path context from the whitespace, which then causes errors in the project output. If your project uses the HL7 IG Autobuild, auto builds will fail after SUSHI 2.0.0 comes out of beta.

Preferred Solution: The preferred way to fix this problem is to update your FSH definitions so that the keywords and rules all start on the first column of each line. This means removing all whitespace before keywords and * rule markers. This does not require any changes to the actual rule text; only the whitespace before the *. You can test your fixes by installing the latest SUSHI 2.0 beta via the following command: npm install -g fsh-sushi@beta.

Alternate Solution: If it is not feasible to make these changes in a timely manner, you can "lock in" the version of SUSHI that the IG Publisher uses by creating or updating a fsh.ini file at the root of your project. For example, the following fsh.ini file would tell the IG Publisher to always use SUSHI 1.3.2, even after SUSHI 2.0.0 is released:

[FSH]
sushi-version=1.3.2

Timeline: In order to avoid being affected by the official SUSHI 2.0.0 release, we recommend you implement one of the above solutions by July 6, 2021.

More Information / Questions: For more information about SUSHI 2.0, you can read the SUSHI 2.0.0 Beta 1 Release Notes. If you have questions, you can reach out to the SUSHI team via the #shorthand stream on Zulip or by logging an issue on SUSHI.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.