As the publisher processes the bundles specified in the ig, it creates html pages for each resource. If the same resource is present in more than one of the bundles, then it will throw an error stating the resource is being generated twice. The work to generate those files using the ig.json and ig xml is expensive, so I removed the duplicate resources from the bundles. This leads to incomplete bundle examples. Need to find a reasonable workaround or reconfigure the bundle processing to not err when duplicate resources are encountered.
Here is a list of the resources removed from each bundle (and where the resource can be found):
- load-patient-12215
- Practitioner-12208 (located in load-patient-12214)
- Organization-2002 (located in load-patient-12214)
- load-patient-12216
- Practitioner-12208
- Organization-2002
- load-patient-12217
- Practitioner-12208
- Organization-2002
- load-patient-12218
- Practitioner-12208
- Organization-2002
- load-patient-12219
- Practitioner-12208
- Organization-2002
- load-patient-12235
- Encounter-51 (located in load-patient-12217)
- Encounter-52 (located in load-patient-12217)
- load-patient-12236
- Practitioner-12226 (located in load-patient-12235)
- Encounter-69 (located in load-patient-12218)
- Encounter-70 (located in load-patient-12218)
- Encounter-71 (located in load-patient-12218)
- Condition-79 (located in load-patient-12218)
As the publisher processes the bundles specified in the ig, it creates html pages for each resource. If the same resource is present in more than one of the bundles, then it will throw an error stating the resource is being generated twice. The work to generate those files using the ig.json and ig xml is expensive, so I removed the duplicate resources from the bundles. This leads to incomplete bundle examples. Need to find a reasonable workaround or reconfigure the bundle processing to not err when duplicate resources are encountered.
Here is a list of the resources removed from each bundle (and where the resource can be found):