generated from openhie/empty-fhir-ig-custom
-
Notifications
You must be signed in to change notification settings - Fork 2
/
ig.ini
53 lines (38 loc) · 1.73 KB
/
ig.ini
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
[IG]
# ini file for the Implementation Guide publisher
# see comments below for instructions
ig = fsh-generated/resources/ImplementationGuide-jembi.starter.ig.json
#template = openhie.fhir.template#current
template = local-template
#template = fhir.base.template#current
#template = cqf.fhir.template#0.7.1
##########################
### ig.ini parameters: ###
##########################
# ig: the name of the implementation guide resource file.
examples:
# ig = input/myig.xml
# ig = input/implementationguide-example2.xml
# For sushi-generated IG (via sushi.config.yaml):
# ig = fsh-generated/resources/myig.json
# template: the IG template that will be used to create the implementation guide (normally be a package name, but can be a local folder).
# base fhir template:
#template = fhir.base.template#current
# HL7 (non-FHIR) IG template:
#template = hl7.base.template#current
# HL7 FHIR template:
#template = hl7.fhir.template#current
# it's possible to specify a specific version of the template
#template = fhir.base.template#1.0.1
# or the current version:
#template = fhir.base.template#current
# if no version is specified, the publisher will take the #current version
# local templates can be used by prefixing a relative path with # :
#template = #mylocaltemplate
#template = #..\templates\mytesttemplate1
# local templates can also use absolute paths:
#template = #C:\MyWork\ImplementationGuides\mytemplates\mytesttemplate1
# other parameters are defined in the ImplementationGuide resource:
# https://confluence.hl7.org/display/FHIR/Implementation+Guide+Parameters
# for more documentation on implementation guides and templates, see the FHIR Guidance ImplementationGuide
# http://build.fhir.org/ig/FHIR/ig-guidance