Difference between revisions of "DoF 2017-MAY-HL7-CAT-Madrid"
John rhoads (talk | contribs) (Initial Madrid FHIR Connectathon content based on Cleveland connectathon page) |
John rhoads (talk | contribs) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 41: | Line 41: | ||
== Activities == | == Activities == | ||
| − | Stefan Karl from Philips Healthcare Patient Monitoring, Boeblingen, Germany (stefan.karl@philips.com), was not able to attend the Connectathon but contributed an example bundle resource showing the linked use of Patient, Observation, Device, multiple DeviceComponent and DeviceMetric resources to represent both the hierarchical structure of the components of a monitor, background information on the metrics reported, and the quantitative results. | + | Stefan Karl from Philips Healthcare Patient Monitoring, Boeblingen, Germany (stefan.karl@philips.com), was not able to attend the Connectathon but contributed an example bundle resource showing the linked use of Patient, Observation, Device, multiple DeviceComponent and DeviceMetric resources to represent both the hierarchical structure of the components of a physiological monitor reporting ECG heart rate and pulse oximeter oxygen saturation, background information on the metrics reported, and the quantitative results. |
The participants on site used this example to explore creating StructureDefinition resources ("profiling") constraining the various components to conform to the model of the device and allow validation of the example bundle using simplifier.net and the Forge tool. | The participants on site used this example to explore creating StructureDefinition resources ("profiling") constraining the various components to conform to the model of the device and allow validation of the example bundle using simplifier.net and the Forge tool. | ||
| Line 48: | Line 48: | ||
== Reference Information == | == Reference Information == | ||
| + | |||
| + | :* [[Media:Devices in FHIR Profiles and Examples.zip | Zip file with example Transaction.xml file and profiles for (partial) validation of it]] | ||
| + | |||
| + | :* [[Media:Devices_on_FHIR.PPTX | Short presentation on Device Track activities given at end of Madrid FHIR Connectathon]] | ||
:* [[DoF_Semantic_Content_Mapping | DoF Semantic Content Mapping (top level page)]] | :* [[DoF_Semantic_Content_Mapping | DoF Semantic Content Mapping (top level page)]] | ||
Latest revision as of 21:49, 25 May 2017
Contents
2017 HL7 WGM, Madrid, Spain - Device Track at FHIR Connectathon May 6-7
Participants
These organizations and individuals participated in the DoF event:
| Organization | Participant | |
|---|---|---|
| Furore | Michel Rutten | m.rutten@furore.com |
| Furore | Rien Wertheim | rien.wertheim@furore.com |
| Philips | John Rhoads | john.rhoads@philips.com |
| Gevity | Iryna Roy | iroy@gevityinc.com |
| Kainos | Sylwester Gryzio | s.gryzio@kainos.com |
| Kainos | K. Suchomski | ksuchomski@kainos.com |
Activities
Stefan Karl from Philips Healthcare Patient Monitoring, Boeblingen, Germany (stefan.karl@philips.com), was not able to attend the Connectathon but contributed an example bundle resource showing the linked use of Patient, Observation, Device, multiple DeviceComponent and DeviceMetric resources to represent both the hierarchical structure of the components of a physiological monitor reporting ECG heart rate and pulse oximeter oxygen saturation, background information on the metrics reported, and the quantitative results.
The participants on site used this example to explore creating StructureDefinition resources ("profiling") constraining the various components to conform to the model of the device and allow validation of the example bundle using simplifier.net and the Forge tool.
This proved to be a relatively complex exercise, which stimulated some fixes and improvements by Michel, who is the lead developer of Forge. An unresolved issue, for a future workaround, was the difficulty of validating the references between the contained resources due to the normal replacement of the references by the server.
