-
Notifications
You must be signed in to change notification settings - Fork 3
Expand file tree
/
Copy pathPhdImplementationGuide.xml
More file actions
632 lines (628 loc) · 27.7 KB
/
Copy pathPhdImplementationGuide.xml
File metadata and controls
632 lines (628 loc) · 27.7 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
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
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
<?xml version="1.0" encoding="UTF-8"?>
<!-- How to use Lloyd's Framework IG
The Frameworks directory is not touched (except for a single hardcoded error that may be fixed in the future).
You may want to rename the *.bat files appropriate for your IG, this example has 'Phd' all over the place.
The source-generated directory is built by the _PhdUpdatePublisher.bat file. It must be generated before being used in the continuous integration build
One can safely delete the source-generated directory and run _PhdUpdatePublisher.bat to rebuild it.
You will need to modify the ig.json file to point to your ImplementationGuide.xml file which is in the src directory
In this example the name of the ImplementationGuide is 'PhdImplementationGuide.xml'.
So in the end all your work is in the src directory.
The resources are placed in the src/resources directory
The Value Sets can be placed in src/vocabulary directory (have not tried this) but putting them in the resources directory is also okay
The pages are placed in the src/pagecontent directory
The menu items that occur across the header in the published guide is in the src/includes directory in the menu.xml file.
These directory names are fixed. (There might be a special directory name for Code Systems but I do not know.)
You need a 'jurisdiction' element or it will not build. Not sure how it is used or why it is required. It is not required by FHIR.
Resources:
The names of the files must follow a certain structure. There are certain options. Here is one that works
1. For structure definitions *.structuredefinition.xml where '*' is your choice (no spaces). Make sure the 'id' and 'name' values are the same as '*'
For example I have PhdNumericObservation.structuredefinition.xml with <id value="PhdNumericObservation" /> and <name value="PhdNumericObservation" />
2. For value sets *.valueset.xml where '*' is your choice (no spaces). Make sure the 'id' and 'name' values are the same as '*'
3. For code systems *.codesystem.xml where '*' is your choice (no spaces). Make sure the 'id' and 'name' values are the same as '*'
4. These resources will not be listed by the Artifacts page unless one specifies a 'grouping' under the 'definition' element and then references
it in each resource with groupingId.
Pages:
For md (markdown) pages (the only pages I know how to do)
1. No spaces in the name
2. No YAML headers to cause the publisher to convert them to html
3. No Jekyll liquid syntax to link to other pages.
4. All references to your pages are 'pageName.html' even though they are written in md.
5. Don't put a title in your md file as it is taken from the 'title' tag in the <page> entry of this file, for example
<title value="Technical Implementation Guidance"/>. If you do you will have two titles.
In your structure definition the first page SHALL be toc.html. This page is auto generated, you do not need to create it
Under this page every page you want included in the table of contents will appear as a sub page.
The next primary page is 'artifacts.html'. This is auto-generated. You need no sub-pages. This topic will cause a list of all your resources to appear
when you click on the 'Artifacts Index' header in the published guide. Be sure to include that name in the 'menu.xml' file in the includes directory
along with the 'Table of Contents' entry.
The other entries are up to you BUT there is a catch. When putting in your pages in the ImplementationGuide the <nameUrl value="pageName.html"/>
even though the file names are 'pageName.md'. But the <generation value="markdown" />.
Make sure the version in the src/properties.txt file is the same as the versions in you value sets and code systems
The 'menu.xml' file in src/includes contains the headers or sections displayed across the top.
In this example there are only xml structure definitions, value sets, code systems, and markdown pages that are all text. -->
<ImplementationGuide xmlns="http://hl7.org/fhir"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://hl7.org/fhir/src-generated/schemas/fhir-single.xsd">
<id value="hl7.fhir.uv.phd"/>
<url value="http://hl7.org/fhir/uv/phd/ImplementationGuide/hl7.fhir.uv.phd"/>
<version value="2.1.0"/>
<name value="PhdImplementationGuide"/>
<title value="Personal Health Device Implementation Guide"/>
<status value="active"/>
<language value="en-US"/>
<extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
<valueCode value="trial-use" />
</extension>
<extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
<valueInteger value="1" />
</extension>
<experimental value="false"/>
<publisher value="HL7 International / Health Care Devices"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/healthcaredevices"/>
</telecom>
</contact>
<!-- Don't know why we should have this except that the build will fail without it -->
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
</coding>
</jurisdiction>
<packageId value="hl7.fhir.uv.phd" />
<extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="dev"/>
</extension>
<fhirVersion value="4.0.1"/>
<!-- declare dependency on PoCD IG for measurement status CodeSystem -->
<dependsOn id="pocd">
<uri value="http://hl7.org/fhir/uv/pocd/ImplementationGuide/hl7.fhir.uv.pocd"/>
<packageId value="hl7.fhir.uv.pocd"/>
<version value="0.3.0"/>
</dependsOn>
<definition>
<resource>
<reference>
<reference value="StructureDefinition/PhdBaseObservation"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="StructureDefinition/PhdNumericObservation"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="StructureDefinition/PhdCompoundObservation"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="StructureDefinition/PhdCompoundNumericObservation"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="StructureDefinition/PhdCodedEnumerationObservation"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="StructureDefinition/PhdBitsEnumerationObservation"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="StructureDefinition/PhdRtsaObservation"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="StructureDefinition/PhdStringObservation"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="StructureDefinition/PhdCoincidentTimeStampObservation"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="StructureDefinition/PhdDevice"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="StructureDefinition/PhdDeviceMetric"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="StructureDefinition/PhgDevice"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="StructureDefinition/PhdPatient"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="StructureDefinition/Accuracy"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="StructureDefinition/Confidence95"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="StructureDefinition/SimpleAlerting"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="CodeSystem/ContinuaDeviceIdentifiers"/>
</reference>
<description value="Codes that identify the device 'identifier', such as whether an EUI is a system id, Bluetooth address, or Ethernet MAC address"/>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="CodeSystem/SimpleAlertOperationalStatesCS"/>
</reference>
<name value="SimpleAlertOperationalStates CodeSystem"/>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="CodeSystem/ASN1ToHL7"/>
</reference>
<description value="Codes for the IEEE 11073-10206 BITs measurement bit values. For example, 150604.0 is the code for Mder bit 0 in measurement type 150604 which is a pulse oximeter device and sensor status. The description of that code is 'Indicates the device is not connected with the sensor'. This code system will grow as more BITs measurements are defined in specializations"/>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="CodeSystem/ContinuaHFS"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="CodeSystem/ContinuaPHDInterfaceIDs"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="CodeSystem/ACMEIncPrivateMDCCodes"/>
</reference>
<exampleBoolean value="true"/>
</resource>
<resource>
<reference>
<reference value="CodeSystem/PhdObservationCategories"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="ValueSet/MDCValueSet"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="ValueSet/MDCnotObject"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="ValueSet/ASN1DeviceBits"/>
</reference>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="ValueSet/ASN1MeasurementBits"/>
</reference>
<description value="Value set for those Asn1ToHL7 codes whose source is a measurement attribute; one of the Enum-observed-value attributes."/>
<exampleBoolean value="false"/>
</resource>
<!-- these value sets were missing -->
<resource>
<reference>
<reference value="ValueSet/DeviceTypes11073MDC"/>
</reference>
<name value="Device Type Specialization IEEE 11073-10101 Nomenclature Codes"/>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="ValueSet/SimpleAlertOperationalStates"/>
</reference>
<name value="Simple Alert Operational States Value Set"/>
<exampleBoolean value="false"/>
</resource>
<resource>
<reference>
<reference value="ValueSet/MDCobject"/>
</reference>
<name value="IEEE 11073 MDC Object infrastructure and Device nomenclature"/>
<exampleBoolean value="false"/>
</resource>
<!-- end of missing value sets -->
<resource>
<reference>
<reference value="CapabilityStatement/PhdFHIRServer"/>
</reference>
<name value="PhdFHIRServer"/>
<exampleBoolean value="false"/>
<!-- <groupingId value="capabilities" /> -->
</resource>
<resource>
<reference>
<reference value="Bundle/bundle-example-1"/>
</reference>
<description value="This example shows a full first time transaction Bundle containing Patient, Device, and Observation resources." />
<name value="Example of a first time Bundle upload"/>
<exampleBoolean value="true"/>
</resource>
<resource>
<reference>
<reference value="Device/phd-74E8FFFEFF051C00.001C05FFE874"/>
</reference>
<name value="Example of PHD Device"/>
<description value="This example PHD Device resource is referenced by other examples and is present for the validator." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdDevice"/>
</resource>
<resource>
<reference>
<reference value="Bundle/bundle-continuousnonin"/>
</reference>
<name value="Example Bundled upload"/>
<description value="This example is an upload from a Bluetooth Low Energy Pulse oximeter device streaming data. In this case the gateway has previously uploaded measurements and saved the logical ids of the Patient and Device resources so they are not re-uploaded." />
</resource>
<resource>
<reference>
<reference value="DeviceMetric/bp-devicemetric-example"/>
</reference>
<name value="Example Phd Device Metric"/>
<description value="This example is a PhdDeviceMetric for a Blood Pressure measurement." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdDeviceMetric"/>
</resource>
<resource>
<reference>
<reference value="Observation/numeric-spotnumeric"/>
</reference>
<name value="Example of a numeric."/>
<description value="This example is a simple numeric observation of a pulse rate from a pulse oximeter. This particular example also has a component as the original measurement has a Supplemental Information attribute indicating that this is a SPOT measurement (a stable average)." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdNumericObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/numeric-spo2-alarm"/>
</reference>
<name value="Example of a numeric with an alert."/>
<description value="This example is a simple numeric observation from a pulse oximeter with an alert." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdNumericObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/temperature-observation"/>
</reference>
<name value="Example of a numeric body temperature observation."/>
<description value="This example is a simple numeric observation of a health thermometer." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdNumericObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/glucose-observation"/>
</reference>
<name value="Example of a numeric glucose observation."/>
<description value="This example is a simple numeric observation of a (continuous) glucose monitor." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdNumericObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/rtsa-example-2"/>
</reference>
<name value="Example 2 of an RTSA"/>
<description value="ECG waveform with scaling" />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdRtsaObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/rtsa-example"/>
</reference>
<name value="Example 1 of an RTSA"/>
<description value="This example is an RTSA observation of a pleth signal from a pulse oximeter. This very short waveform maps to a valueSampledData element." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdRtsaObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/numeric-observation-not-a-number"/>
</reference>
<name value="Example of a NaN case"/>
<description value="This example contains a NaN (not a number) measurement." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdNumericObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/meal-context-observation"/>
</reference>
<name value="Example of coded enumeration"/>
<description value="This example contains measurement that is itself a code. The measurement comes from a Glucose meter and indicates that the glucose measurement was taken after lunch or dinner. It is also known as the meal context." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCodedEnumerationObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/bits-observation"/>
</reference>
<name value="Example of a ASN1 BITs measurement from a Pulse Oximeter"/>
<description value="This example is a device and sensor status measurement from a pulse oximeter." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdBitsEnumerationObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/bpm-status"/>
</reference>
<name value="Example of a BPM status report"/>
<description value="This example reports the status of a BPM measurement." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdBitsEnumerationObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/compound-numeric-blood-pressure"/>
</reference>
<name value="Example of a compound numeric observation"/>
<description value="This example is from a Blood Pressure cuff." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCompoundNumericObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/compound-numeric-blood-pressure-no-mean"/>
</reference>
<name value="Example of a compound numeric observation with one component value absent"/>
<description value="This example is from a Blood Pressure cuff." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCompoundNumericObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/compound-observation-glucose"/>
</reference>
<name value="Example of a compound observation"/>
<description value="This artificial example combines a glucose measurement and context information." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCompoundObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/stringenum-1234"/>
</reference>
<name value="Example of String measurement 1"/>
<description value="This example observation reports some arbitrary text from a cardiavascular fitness device." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdStringObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/string-observation-1"/>
</reference>
<name value="Example of String measurement 2"/>
<description value="This example observation reports some arbitrary text from a Glucose meter explaining the failure of the measurement." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdStringObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/coin-20181119202022"/>
</reference>
<name value="Example of a Coincident Timestamp PHG better synchronized"/>
<description value="This example is a Coincident Timestamp where the PHG is better synchronized to NTP time than the PHD." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCoincidentTimeStampObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/coin-example-timefault"/>
</reference>
<name value="Example of a Coincident Timestamp with a Time Fault"/>
<description value="This example is a Coincident Timestamp where the PHD has a time fault; it's current timeline is unknown and it reported timestamps in its measurements." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCoincidentTimeStampObservation"/>
</resource>
<resource>
<reference>
<reference value="Device/phd-711000FEFF5F49B0.B0495F001071"/>
</reference>
<name value="Example of a Blood Pressure PHD"/>
<description value="This example maps the MDS data from a Blood Pressure PHD. This device did not report Reg-Cert-Data-List information." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdDevice"/>
</resource>
<resource>
<reference>
<reference value="Device/phd-00601900010E9234.F45EABA80832"/>
</reference>
<name value="Example of a Glucose Monitor PHD"/>
<description value="This example maps an Glucose monitor PHD. It is referenced by a coded Glucose meal context observation" />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdDevice"/>
</resource>
<resource>
<reference>
<reference value="Observation/coin-20181119174911"/>
</reference>
<name value="Example of a Coincident Timestamp referenced from BP observation"/>
<description value="This Coincident Timestamp observation is referenced by the Blood Pressure Observation" />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCoincidentTimeStampObservation"/>
</resource>
<resource>
<reference>
<reference value="Observation/coin-example-1"/>
</reference>
<name value="Example of a Coincident Timestamp"/>
<description value="This Coincident Timestamp observation is referenced by other Observation examples." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCoincidentTimeStampObservation"/>
</resource>
<resource>
<reference>
<reference value="Device/phg-ecde3d4e58532d31.000000000000"/>
</reference>
<name value="Example of a Gateway"/>
<description value="This example maps an Android Gateway" />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhgDevice"/>
</resource>
<resource>
<reference>
<reference value="Device/phg-example"/>
</reference>
<name value="Example of a Gateway 2"/>
<description value="This example maps an Android Gateway" />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhgDevice"/>
</resource>
<resource>
<reference>
<reference value="Patient/patientExample-1"/>
</reference>
<name value="Example of a known Patient"/>
<description value="This example maps a known patient where an optional patient name is included." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdPatient"/>
</resource>
<resource>
<reference>
<reference value="Patient/patientExample-2"/>
</reference>
<name value="Example of an unknown Patient"/>
<description value="This example maps an unknown patient." />
<exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdPatient"/>
</resource>
<!-- The 'toc' or table of contents is required and must appear first in the pages list
and it must have the name toc.html. The toc.html is generated and its contents are determined
by all the pages contained in the hierarchy underneath it. The first page underneath it
is the home page index.html which shall be named 'index'. In this guide it is an md file
that I have written. The second 'primary' page SHALL be artifacts.html and it has no sub-pages. -->
<page>
<nameUrl value="toc.html"/>
<title value="Table of Contents"/>
<generation value="html"/>
<!-- Now for the structure of the table of contents -->
<page>
<nameUrl value="index.html"/>
<title value="Personal Health Device Implementation Guide Home Page"/>
<generation value="markdown"/>
<page>
<nameUrl value="UseCases.html"/>
<title value="Use Cases"/>
<generation value="markdown"/>
</page>
<page>
<nameUrl value="ProfilesOverview.html"/>
<title value="Profiles Overview"/>
<generation value="markdown"/>
</page>
<page>
<nameUrl value="Organizations.html"/>
<title value="Organizations"/>
<generation value="markdown"/>
</page>
<page>
<nameUrl value="Glossary.html"/>
<title value="Glossary"/>
<generation value="markdown"/>
</page>
</page>
<page>
<nameUrl value="ProfileConsumers.html"/>
<title value="Consuming the PHD Profile FHIR Resources"/>
<generation value="markdown"/>
</page>
<page>
<nameUrl value="TechnicalImplementationGuidance.html"/>
<title value="PHG Implementation Guidance"/>
<generation value="markdown"/>
<page>
<nameUrl value="RemotePatientMonitoringConsiderations.html"/>
<title value="Remote Patient Monitoring Considerations"/>
<generation value="markdown"/>
</page>
<page>
<nameUrl value="GenericModel.html"/>
<title value="Generic and Extensible Model"/>
<generation value="markdown"/>
</page>
<page>
<nameUrl value="DIMtoFHIRMapping.html"/>
<title value="DIM to FHIR Mapping"/>
<generation value="markdown"/>
<page>
<nameUrl value="MderFLOATsandSFLOATs.html"/>
<title value="IEEE 11073 FLOATs and SFLOATs"/>
<generation value="markdown"/>
</page>
<page>
<nameUrl value="Nomenclaturecodes.html"/>
<title value="IEEE 11073-10101 MDC Nomenclature codes"/>
<generation value="markdown"/>
</page>
<page>
<nameUrl value="GeneratingtheTimeStampPartIdentifier.html"/>
<title value="Generating the PHD Reported Timestamp Identifier"/>
<generation value="markdown"/>
</page>
</page>
<page>
<nameUrl value="CoincidentTimeStamp.html"/>
<title value="Coincident Timestamp"/>
<generation value="markdown"/>
</page>
<page>
<nameUrl value="Non11073PHDDevices.html"/>
<title value="Non IEEE 11073 PHD Devices"/>
<generation value="markdown"/>
</page>
</page>
<!-- Required element, a top-level page. The content is generated -->
<page>
<nameUrl value="artifacts.html"/>
<title value="Artifact List"/>
<generation value="html"/>
</page>
<page>
<nameUrl value="changes.html"/>
<title value="Change Log"/>
<generation value="markdown"/>
</page>
<!-- to fix recent warnings from the tooling-->
<page>
<nameUrl value="Appendix.html"/>
<title value="Appendix"/>
<generation value="markdown"/>
</page>
</page>
<parameter>
<code value="copyrightyear"/>
<value value="2016+"/>
</parameter>
<parameter>
<code value="releaselabel"/>
<value value="STU 2.0"/>
</parameter>
<parameter>
<code value="shownav"/>
<value value="true"/>
</parameter>
</definition>
</ImplementationGuide>