-
Notifications
You must be signed in to change notification settings - Fork 5
/
sushi-config.yaml
192 lines (179 loc) · 7.45 KB
/
sushi-config.yaml
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
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
# This IG YML file is inspired by the ImplementationGuide resource
# and also draws from package.json, package-list.json, and ig.ini.
# That said, it is structured for ease-of-use, so it is not strictly
# conformant to any of those existing configuration formats.
# SUSHI will use id as both id and packageId in the IG unless a
# specific packageId is also provided in this file.
id: hl7.fhir.uv.crmi
canonical: http://hl7.org/fhir/uv/crmi
name: CRMI
title: Canonical Resource Management Infrastructure Implementation Guide
description: >-
This implementation guide defines profiles, operations, capability statements
and guidance to facilitate the content management lifecycle for authoring,
publishing, distribution, and implementation of FHIR knowledge artifacts such
as value sets, profiles, libraries, rules, and measures. The guide is
intended to be used by specification and content implementation guide authors
as both a dependency for validation of published artifacts, and a guide for
construction and publication of content.
status: active
license: CC0-1.0
date: 2024-05-08
version: 1.1.0-cibuild
# Although fhirVersions is 0..* in the ImplementationGuide resource
# it can be a single item OR and array here (but so far SUSHI only
# supports 4.0.1 anyway).
fhirVersion: 4.0.1
# The following two lines correspond to items that used to be in
# ig.ini but were moved to IG.definition.parameter. For
# consistency within this file, the names are represented using
# camelcase, but if authors use the formal parameter names, SUSHI
# will recognize them as well. In either case, they'll be copied
# to the IG JSON using the formal names.
copyrightYear: 2022+
releaseLabel: cibuild
# The publisher can be a single item or a list, each with a name and
# optional url and/or email. The first publisher's name will be used
# as IG.publisher. The contact details and/or additional publishers
# will be translated into IG.contact values.
publisher:
name: HL7 International / Clinical Decision Support
extension:
- url: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
valueCode: cds
# Those who need more control or want to add additional details to the contact values can use
# contact directly and follow the format outlined in the ImplementationGuide resource and
# ContactDetail.
contact:
- telecom:
- system: url
value: http://www.hl7.org/Special/committees/dss
# The jurisdiction can be a single item or a list. The FHIR Shorthand
# code syntax can be used here.
jurisdiction: http://unstats.un.org/unsd/methods/m49/m49.htm#001 "World"
# The dependencies property corresponds to IG.dependsOn. The key is the
# package id and the value is the version (or dev/current). For advanced
# use cases, the value can be an object with keys for `uri` and `version`.
# For R5 ImplementationGuides, the object can also have a key for `reason`.
# dependencies:
# fhir.cqf.common: 4.0.1
# hl7.fhir.uv.extensions.r4: 1.0.0
dependencies:
hl7.terminology: 5.5.0
hl7.fhir.uv.extensions.r4:
id: ext
version: 5.1.0
parameters:
excludettl: true
path-history: http://hl7.org/fhir/uv/crmi/history.html
path-expansion-params: '../../input/_resources/exp-params.json' # for using International ed of SNOMED
special-url:
- http://terminology.hl7.org/ValueSet/artifact-resource-types
auto-oid-root: 2.16.840.1.113883.4.642.40.38
apply:
- version
- date
- status
- publisher
- contact
- copyright
- experimental
- jurisdiction
pages:
index.md:
title: Home
introduction.md:
title: Introduction
artifact-lifecycle.md:
title: Artifact Lifecycle
version-manifest.md:
title: Artifact Manifest
artifact-conventions.md:
title: Artifact Conventions
packaging.md:
title: Packaging
testing.md:
title: Testing
publishing.md:
title: Publishing
distribution.md:
title: Distribution
profiles.md:
title: Profiles
extensions.md:
title: Extensions
operations.md:
title: Operations
capabilities.md:
title: Capabilities
artifact-repository-service.md:
title: Artifact Repository Service
artifact-terminology-service.md:
title: Artifact Terminology Service
terminology.md:
title: Terminology
artifacts.xml:
title: Artifacts Summary
downloads.md:
title: Downloads
changes.md:
title: Version History
# The resources property corresponds to IG.definition.resource.
# SUSHI can auto-generate all of the resource entries based on
# the FSH definitions and/or information in any user-provided
# JSON or XML resource files. If the generated entries are not
# sufficient or complete, however, the author can add entries
# here. If the reference matches a generated entry, it will
# replace the generated entry. If it doesn't match any generated
# entries, it will be added to the generated entries. The format
# follows IG.definition.resource with the following differences:
# * use IG.definition.resource.reference.reference as the YAML key.
# * if the key is an id or name, SUSHI will replace it with the
# correct URL when generating the IG JSON.
# * specify "omit" to omit a FSH-generated resource from the
# resource list.
# * if the exampleCanonical is an id or name, SUSHI will replace
# it with the correct canonical when generating the IG JSON.
# * groupingId can be used, but top-level groups syntax may be a
# better option (see below).
# The following are simple examples to demonstrate what this might
# look like:
#
# resources:
# ImplementationGuide/hl7.fhir.uv.cpg.chf: omit #omit this because this template does not generate HTML for IG, so the link from TOC fails
# Patient/my-example-patient:
# name: My Example Patient
# description: An example Patient
# exampleBoolean: true
# Patient/bad-example: omit
resources:
Group/definition-example:
name: Example Group Definition
description: Example Group Definition illustrating the use of an expression to define group membership.
Device/cqf-tooling:
name: CQF Tooling Device
description: Example of a Software System Device instance for describing tooling that was used to process artifacts. This resource is typically referenced from the `crmi-softwaresystem` extension
Medication/definition-example:
name: Example Medication Definition
description: Example of a Medication resource illustrating use as a definitional artifact.
MedicationKnowledge/definition-example:
name: Example MedicationKnowledge Definition
description: Example of a MedicationKnowledge resource illustrating use as a definitional artifact.
Substance/artifact-reference-example:
name: Example Substance Definition
description: Example of a Substance resource illustrating use as a definitional artifact.
MeasureReport/result-example:
name: Example MeasureReport
description: Example MeasureReport illustrating use of MeasureReport as a test case.
Parameters/crmi-evaluationresult-example:
name: Example Evaluation Result Parameters
description: Example Parameters resource demonstrating the use of data-absent-reason extension to indicate a null evaluation result.
Group/testcase-example:
name: Example TestCase Group
description: Example Group illustrating use of the cqf-testArtifact extension to build a set of test data for an artifact.
Patient/example-1:
name: Patient Example 1
description: Example patient 1 in the test case group
Patient/example-2:
name: Patient Example 2
description: Example patient 2 in the test case group