-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathsushi-config.yaml
More file actions
162 lines (149 loc) · 6.09 KB
/
Copy pathsushi-config.yaml
File metadata and controls
162 lines (149 loc) · 6.09 KB
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
# documentation: https://fshschool.org/docs/sushi/configuration/
#
id: hl7.fhir.uv.smart-health-cards-and-links
canonical: http://hl7.org/fhir/uv/smart-health-cards-and-links
name: SMART Health Cards and Links
title: SMART Health Cards and Links IG
description: FHIR Implementation Guide for SMART Health Cards and Links
status: active # draft | active | retired | unknown
version: 1.0.0
fhirVersion: 4.0.1 # https://www.hl7.org/fhir/valueset-FHIR-version.html
copyrightYear: 2024+
releaseLabel: STU 1 # CI Build | STU1 Ballot
license: CC0-1.0
jurisdiction: http://unstats.un.org/unsd/methods/m49/m49.htm#001 "World"
publisher:
name: HL7 International / FHIR Infrastructure
url: http://www.hl7.org/Special/committees/fiwg
parameters:
jira-code: uv-smart-health-cards-and-links
# FHIR-uv-smart-health-cards-and-links
#dependencies:
# hl7.fhir.uv.extensions.r4:
# id: ext
# version: 5.1.0
# hl7.terminology: 5.5.0
#dependencies:
# hl7.fhir.us.core:
# id: uscore
# version: 3.1.1
# reason: |
# Defines U.S. EHR expectations on a range of resources that will be passed to and/or queried by REMS CDS servers
# hl7.fhir.uv.smart-app-launch:
# id: SmartAppLaunch
# version: 2.1.0
# reason: |
# Defines base expectations and profiles for SMART app launch requirements
#
#
pages:
index.md:
title: Home Page
cards-user-stories.md:
title: Health Cards User Stories
cards-specification.md:
extension:
- url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
valueCode: trial-use
title: Health Cards Specification
cards-credential-modeling.md:
title: Credential Modeling
cards-examples.md:
title: Health Cards Examples
frequently-asked-questions.md:
title: Frequently Asked Questions
cards-changelog.md:
title: Health Cards Change Log
links-user-stories.md:
title: Health Links User Stories
links-specification.md:
extension:
- url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
valueCode: trial-use
title: Health Links Specification
links-examples.md:
title: Health Links Examples
glossary.md:
title: Glossary
downloads.xml:
title: Downloads
history.md:
title: Change Log
contact:
- name: Frank McKinney
telecom:
- system: email # phone | fax | email | pager | url | sms | other
value: frank.mckinney@pocp.com
- system: email # phone | fax | email | pager | url | sms | other
value: fm@frankmckinney.com
extension:
- url: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
valueCode: fhir
- url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
valueCode: trial-use
- url: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
valueInteger: 4
resources:
#----------- Examples -------------
Binary/shl-payload-1:
extension:
- url: http://hl7.org/fhir/tools/StructureDefinition/implementationguide-resource-format
valueCode: application/fhir+json
name: "Example SHL Payload 1"
description: "Example of a SMART Health Links Payload object containing all properties."
Binary/shl-payload-2:
extension:
- url: http://hl7.org/fhir/tools/StructureDefinition/implementationguide-resource-format
valueCode: application/fhir+json
name: "Example SHL Payload 2"
description: "Example of a minimal SMART Health Links Payload object."
Binary/shl-manifest-1:
extension:
- url: http://hl7.org/fhir/tools/StructureDefinition/implementationguide-resource-format
valueCode: application/fhir+json
name: "Example SHL Manifest 1"
description: "Example of a SMART Health Links Manifest including optional properties."
# using exampleCanonical causes an error if the example doesn't contain a "resourceType" element, which isn't part of an actual instance
# exampleCanonical: http://hl7.org/fhir/uv/smart-health-cards-and-links/StructureDefinition/ShlPayload
# Using the extension below instead of exampleCanonical didn't appear to do anything... the example was included in the IG and no error related to resourceType was generated.
# But the example wasn't associated with its logical model
# - url: http://hl7.org/fhir/tools/StructureDefinition/implementationguide-resource-logical
# valueCanonical: http://hl7.org/fhir/uv/smart-health-cards-and-links/StructureDefinition/ShlPayload
#auto-oid-root: tbd
# * 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