generated from IHE/supplement-template
-
Notifications
You must be signed in to change notification settings - Fork 1
/
sushi-config.yaml
80 lines (73 loc) · 2.74 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
# sushi-config.yaml is documented https://fshschool.org/docs/sushi/configuration/
# ───────────────────────────────────────────────────
# the id should be lowercase made up of "ihe." + {domain acronym} + "." + {profile acronym/short-name}
# e.g. ihe.iti.mhds, or ihe.iti.basicaudit
id: ihe.pcc.ems-overall
canonical: https://profiles.ihe.net/PCC/EMS-Overall
version: 0.1.1-current
name: IHE_PCC_EMS-Overall
title: "EMS Interoperability Solutions"
description: Overall overview of solving the EMS Interoperability needs with IHE-Profiles
releaseLabel: ci-build
#releaseLabel: Trial-Implementation
#date: 2022-01-02
status: active
publisher:
- name: IHE Patient Care Coordination Technical Committee
- url: https://www.ihe.net/ihe_domains/patient_care_coordination/
- email: pcc@ihe.net
contact:
- name: IHE Patient Care Coordination Technical Committee
telecom:
- system: email
value: pcc@ihe.net
license: CC-BY-4.0
fhirVersion: 4.0.1
jurisdiction: 'http://unstats.un.org/unsd/methods/m49/m49.htm#001'
#copyright: IHE http://www.ihe.net/Governance/#Intellectual_Property
copyrightYear: 2023+
parameters: # see https://confluence.hl7.org/display/FHIR/Implementation+Guide+Parameters
path-resource:
- input/resources
- fsh-generated/resources
- input/examples
# path-pages:
# - input/pagecontent
# - fsh-generated/includes
show-inherited-invariants: 'false'
usage-stats-opt-out: 'false'
logging: progress
shownav: 'true'
active-tables: 'false'
apply-contact: 'true'
apply-jurisdiction: 'true'
apply-publisher: 'true'
apply-version: 'true'
resources:
# list every example here with a name, description and that exampleBoolean is true; These are used to populate the artifacts page, and are needed to eliminate build warnings
# You may delay filling out this section until you approach publication as it is merely a nice to have and eliminates build warnings -- If you do this then you will need above the autoload-resources true
pages:
# itemize here each narrative page. Include assigned section numbers when appropriate
index.md:
title: EMS-Overview Home
generation: markdown
pdqdrd.md:
title: Consuming Document Sharing
generation: markdown
publish.md:
title: Publishing in Document Sharing
generation: markdown
pcf.md:
title: 'Use Case: Paramedicine Care Flow'
generation: markdown
ript.md:
title: 'Use Case: Routine Interfacility Patient Transport'
generation: markdown
menu:
Home: index.html
Doc-Sharing:
Consuming: pdqdrd.html
Publishing: publish.html
EMS-Flows:
Paramedicine Care Flow: pcf.html
Routine Interfacility Patient Transport: ript.html