generated from WorldHealthOrganization/smart-ig-empty
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathsushi-config.yaml
264 lines (256 loc) · 10 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
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
id: smart.who.int.pcmt
canonical: http://smart.who.int/pcmt
name: SMARTPCMT
title: SMART Product Catalog
description: Data exchange specifications for Product Catalog supporting the SMART Guidelines
status: draft # draft | active | retired | unknown
version: 0.1.0
fhirVersion: 5.0.0 # https://www.hl7.org/fhir/valueset-FHIR-version.html
copyrightYear: 2023+
releaseLabel: ci-build # ci-build | draft | qa-preview | ballot | trial-use | release | update | normative+trial-use
# license: CC0-1.0 # https://www.hl7.org/fhir/valueset-spdx-license.html
# jurisdiction: urn:iso:std:iso:3166#US "United States of America" # https://www.hl7.org/fhir/valueset-jurisdiction.html
publisher:
name: WHO
url: http://who.int
# email: [email protected]
meta:
profile:
- http://smart.who.int/smart-base/ImplementationGuide-SGImplementationGuide
pages:
index.md:
title: Home
changes.md:
title: Changes
dependencies.md:
title: Dependencies
references.md:
title: References
adapting.md:
title: Adapting Guidelines for Country use
license.md:
title: License
business-requirements.md:
title: Business Requirements
concepts.md:
title: Concepts
personas.md:
title: Generic Personas
scenarios.md:
title: User Scenarios
business-processes.md:
title: Business Processes
dictionary.md:
title: Data Dictionary
decision-logic.md:
title: Decision-support logic
indicators.md:
title: Indicator and Performance Metrics
functional-requirements.md:
title: Functional Requirements
non-functional-requirements.md:
title: Non-functional Requirements
data-models-and-exchange.md:
title: Data Models and Exchange
system-actors.md:
title: System Actors
sequence-diagrams.md:
title: Sequence Diagrams
transactions.md:
title: Transactions
# logical-models.md:
# title: Logical Models
indicators-measures.md:
title: Indicators and Measures
# profiles.xml:
# title: Content profiles
codings.md:
title: Codings
deployment.md:
title: Deployment
security-privacy.md:
title: Security and Privacy Considerations
testing.md:
title: Testing
test-data.md:
title: Test Data
reference-implementations.md:
title: Reference Implementations
trust_domain.md:
title: Trust Domains
downloads.md:
title: Downloads
indices.md:
title: Indices
artifacts.html:
title: Artifact Index
maps.md:
title: Mappings
menu:
Home:
Summary: index.html
Changes: changes.html
Dependencies: dependencies.html
References: references.html
Adapting Guidelines for Country use: adapting.html
Business Requirements:
Concepts: concepts.html
Generic Personas: personas.html
User Scenarios: scenarios.html
Business Processes: business-processes.html
Data Dictionary: dictionary.html
Decision-support Logic: decision-logic.html
Indicator and Performance Metrics: indicators.html
Functional Requirements: functional-requirements.html
Non-functional Requirements: non-functional-requirements.html
Data Models and Exchange:
System Actors: system-actors.html
Sequence Diagrams: sequence-diagrams.html
Transactions: transactions.html
Indicators and Measures: indicators-measures.html
Codings: codings.html
Deployment:
Security and Privacy Considerations: security-privacy.html
Testing: testing.html
Test Data: test-data.html
Reference Implementations: reference-implementations.html
Trust Domains: trust_domain.html
Downloads: downloads.html
Indices:
Artifact Index: artifacts.html
Mappings: maps.html
# ╭───────────────────────────Less Common Implementation Guide Properties──────────────────────────╮
# │ Uncomment the properties below to configure additional properties on the ImplementationGuide │
# │ resource. These properties are less commonly needed than those above. │
# ╰────────────────────────────────────────────────────────────────────────────────────────────────╯
#
# 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:
# - name: Bob Smith
# telecom:
# - system: email # phone | fax | email | pager | url | sms | other
# value: [email protected]
# use: work
#
#
# The global property corresponds to the IG.global property, but it
# uses the type as the YAML key and the profile as its value. Since
# FHIR does not explicitly disallow more than one profile per type,
# neither do we; the value can be a single profile URL or an array
# of profile URLs. If a value is an id or name, SUSHI will replace
# it with the correct canonical when generating the IG JSON.
#
# global:
# Patient: http://example.org/fhir/StructureDefinition/my-patient-profile
# Encounter: http://example.org/fhir/StructureDefinition/my-encounter-profile
#
#
# 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:
# Patient/my-example-patient:
# name: My Example Patient
# description: An example Patient
# exampleBoolean: true
# Patient/bad-example: omit
#
#
# Groups can control certain aspects of the IG generation. The IG
# documentation recommends that authors use the default groups that
# are provided by the templating framework, but if authors want to
# use their own instead, they can use the mechanism below. This will
# create IG.definition.grouping entries and associate the individual
# resource entries with the corresponding groupIds. If a resource
# is specified by id or name, SUSHI will replace it with the correct
# URL when generating the IG JSON.
#
# groups:
# GroupA:
# name: Group A
# description: The Alpha Group
# resources:
# - StructureDefinition/animal-patient
# - StructureDefinition/arm-procedure
# GroupB:
# name: Group B
# description: The Beta Group
# resources:
# - StructureDefinition/bark-control
# - StructureDefinition/bee-sting
#
#
# The ImplementationGuide resource defines several other properties
# not represented above. These properties can be used as-is and
# should follow the format defined in ImplementationGuide:
# * date
# * meta
# * implicitRules
# * language
# * text
# * contained
# * extension
# * modifierExtension
# * experimental
# * useContext
# * copyright
# * packageId
#
#
# ╭──────────────────────────────────────────SUSHI flags───────────────────────────────────────────╮
# │ The flags below configure aspects of how SUSHI processes FSH. │
# ╰────────────────────────────────────────────────────────────────────────────────────────────────╯
# The FSHOnly flag indicates if only FSH resources should be exported.
# If set to true, no IG related content will be generated.
# The default value for this property is false.
#
# FSHOnly: false
#
#
# When set to true, the "short" and "definition" field on the root element of an Extension will
# be set to the "Title" and "Description" of that Extension. Default is true.
#
# applyExtensionMetadataToRoot: true
#
#
# The instanceOptions property is used to configure certain aspects of how SUSHI processes instances.
# See the individual option definitions below for more detail.
#
# instanceOptions:
# Determines for which types of Instances SUSHI will automatically set meta.profile
# if InstanceOf references a profile:
#
# setMetaProfile: always # always | never | inline-only | standalone-only
#
#
# Determines for which types of Instances SUSHI will automatically set id
# if InstanceOf references a profile:
#
# setId: always # always | standalone-only
dependencies:
smart.who.int.base: current
ihe.iti.mcsd:
id: IHE_ITI_mCSD
uri: https://profiles.ihe.net/ITI/mCSD/ImplementationGuide/ihe.iti.mcsd
version: 3.8.0