ddsf:public:guidebook:03_user:02_health
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ddsf:public:guidebook:03_user:02_health [2021/07/14 15:54] murphy ↷ Links adapted because of a move operation |
ddsf:public:guidebook:03_user:02_health [2022/05/12 16:08] (current) mitza [Table] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | DDS====== Use Case 1: Connected Healthcare ====== | + | ====== Use Case 1: Connected Healthcare ====== |
| [[ddsf:public:guidebook:03_user:start| Return to User Experiences]] | [[ddsf:public:guidebook:03_user:start| Return to User Experiences]] | ||
| - | |||
| - | * **<color #FF0000><todo @char>Please Review</todo></color>** | ||
| - | * **<color #FF0000><todo @DDSFmember>Please Review</todo></color>** | ||
| - | |||
| Patient Monitoring in a Maturing Digital World | Patient Monitoring in a Maturing Digital World | ||
| Line 10: | Line 6: | ||
| ===== Details ===== | ===== Details ===== | ||
| - | ^ Author | Matt Grubis | | + | ^ Author | Matt Grubis | |
| - | ^ Title | Chief Engineer | | + | ^ Title | Chief Engineer | |
| - | ^ Organization | GE Healthcare | | + | ^ Organization | GE Healthcare | |
| - | ^ Date | 29 Apr 2020 | | + | ^ Date | 29 Apr 2020 | |
| - | ^ Time | 33 Minutes | | + | ^ Time | 33 Minutes | |
| - | ^ Presentation | [[https://www.brighttalk.com/webcast/12231/397992?utm_campaign=channel-feed&utm_source=brighttalk-portal&utm_medium=web | Connected Healthcare - DDSF BrightTalk ]] | | + | ^ Presentation | [[https://www.brighttalk.com/webcast/12231/397992?utm_campaign=channel-feed&utm_source=brighttalk-portal&utm_medium=web| Connected Healthcare - DDSF BrightTalk ]] | |
| - | ^ Docment | [[https://www.dds-foundation.org/wp-content/uploads/2020/03/Application_Example-DDS_in_Patient_Monitoring_JB76285XX1_DDS-Foundation.pdf | DDS in Patient Monitoring ]] | | + | ^ Document | [[https://www.dds-foundation.org/wp-content/uploads/2020/03/Application_Example-DDS_in_Patient_Monitoring_JB76285XX1_DDS-Foundation.pdf| DDS in Patient Monitoring ]] | |
| ===== Patient Monitoring in a Maturing Digital World ===== | ===== Patient Monitoring in a Maturing Digital World ===== | ||
| Line 95: | Line 91: | ||
| A connected healthcare system needs to plan for patient monitoring with the idea of: | A connected healthcare system needs to plan for patient monitoring with the idea of: | ||
| - | * [[ddsf:private:guidebook:06_append:glossary:r:realtime|real-time]] acquisition of data | + | * [[ddsf:public:guidebook:06_append:glossary:r:realtime|real-time]] acquisition of data |
| * real-time processing of data | * real-time processing of data | ||
| * analysis of the information, and | * analysis of the information, and | ||
| Line 136: | Line 132: | ||
| * **<color dimgray/lightgrey>[gray dots]</color>** To improve patient care, there are convenient viewing stations in the hallways allowing the nurses to quickly assess a patients status without having to go into the room or without having to return to the central station. | * **<color dimgray/lightgrey>[gray dots]</color>** To improve patient care, there are convenient viewing stations in the hallways allowing the nurses to quickly assess a patients status without having to go into the room or without having to return to the central station. | ||
| - | * In addition to the wards ecosystem, the data is also being sent to a central Electronic Medical Record (ERM) and central [[ddsf:private:guidebook:06_append:glossary:s:server|servers]] allowing mobile consults on a phone or a tablet or the doctor is doing a mobile consult from a remote location. | + | * In addition to the wards ecosystem, the data is also being sent to a central Electronic Medical Record (ERM) and central [[ddsf:public:guidebook:06_append:glossary:s:server|servers]] allowing mobile consults on a phone or a tablet or the doctor is doing a mobile consult from a remote location. |
| * The data is also sent to a cloud server where data analytics are larger analytics or population management. | * The data is also sent to a cloud server where data analytics are larger analytics or population management. | ||
| Line 268: | Line 264: | ||
| : There are so many measurements that can be collected from a body, it results in very complex [[ddsf:public:guidebook:06_append:glossary:d:dm]]. Using verbose, un-managed data models like those in HL7 is not efficient and can lead to errors of translation. So, representing the data the data using DDS X-TYPES, the data is ultimately represented as binary data. It is efficient from at the machine level. The data can be sent across the wire in binary format, but is still fully documented and described with XTYPES. So each station shares the same current data model regardless of its computer architecture (i.e., big verus [[ddsf:public:guidebook:06_append:glossary:l:littleendian|little endian]], [[ddsf:public:guidebook:06_append:glossary:0-9:16-bit|16-Bit]], [[ddsf:public:guidebook:06_append:glossary:0-9:32-bit|32-Bit]] or [[ddsf:public:guidebook:06_append:glossary:0-9:64-bit|64-Bit]] processors, etc. | : There are so many measurements that can be collected from a body, it results in very complex [[ddsf:public:guidebook:06_append:glossary:d:dm]]. Using verbose, un-managed data models like those in HL7 is not efficient and can lead to errors of translation. So, representing the data the data using DDS X-TYPES, the data is ultimately represented as binary data. It is efficient from at the machine level. The data can be sent across the wire in binary format, but is still fully documented and described with XTYPES. So each station shares the same current data model regardless of its computer architecture (i.e., big verus [[ddsf:public:guidebook:06_append:glossary:l:littleendian|little endian]], [[ddsf:public:guidebook:06_append:glossary:0-9:16-bit|16-Bit]], [[ddsf:public:guidebook:06_append:glossary:0-9:32-bit|32-Bit]] or [[ddsf:public:guidebook:06_append:glossary:0-9:64-bit|64-Bit]] processors, etc. | ||
| * On the wire compatibility with dynamic data model dynamic changes and evolution. This provides on-wire compatibility which is really important as the data model changes. The data model not only changes through the current care workflow on different machines, but also aa the system is extended and upgraded in the future. For example, providing upward compatibility as parameters are modified or added going forward, or even using new parameters we have not even invented yet. | * On the wire compatibility with dynamic data model dynamic changes and evolution. This provides on-wire compatibility which is really important as the data model changes. The data model not only changes through the current care workflow on different machines, but also aa the system is extended and upgraded in the future. For example, providing upward compatibility as parameters are modified or added going forward, or even using new parameters we have not even invented yet. | ||
| - | * Content aware filtering to drive further efficiency - A lot of our devices are wireless, battery operated and using [[ddsf:private:guidebook:06_append:glossary:w:wan]] connectivity. Sending un-needd or unwanted data to and from these devices can shorten their usefulness or create the the equivalent of a Denial of Service (DoS) attack. Therefore, we have to make sure for efficiency and security that the data transfers are efficient and minimal. In other words, we are not sending data to places in the network that do not need or want the data. So, we rely on the built-in [[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds]] content filtering at both the source and the destination. So we are sending the correct data to the data sinks that require that data and nothing extra. | + | * Content aware filtering to drive further efficiency - A lot of our devices are wireless, battery operated and using [[ddsf:public:guidebook:06_append:glossary:w:wan]] connectivity. Sending un-needd or unwanted data to and from these devices can shorten their usefulness or create the the equivalent of a Denial of Service (DoS) attack. Therefore, we have to make sure for efficiency and security that the data transfers are efficient and minimal. In other words, we are not sending data to places in the network that do not need or want the data. So, we rely on the built-in [[ddsf:public:guidebook:06_append:glossary:d:data_distribution_service_dds]] content filtering at both the source and the destination. So we are sending the correct data to the data sinks that require that data and nothing extra. |
| * Fully secure endpoint authentication and [[ddsf:public:guidebook:06_append:glossary:e:encryption|encryption]] built-in - In healthcare, security is paramount. Making sure that we have military grade security, there is encryption, authentication, authorization and that different nodes have different rights to different topics and different ways of exerting Command and Control (C2) over a patients state (i.e., admitting, discharging, silencing alarms, changing the way an algorithm behaves.) These types of features must be at the foundation of the system, otherwise the entire system at risk. In our system, we are using DDS-Secure to help with these issues. | * Fully secure endpoint authentication and [[ddsf:public:guidebook:06_append:glossary:e:encryption|encryption]] built-in - In healthcare, security is paramount. Making sure that we have military grade security, there is encryption, authentication, authorization and that different nodes have different rights to different topics and different ways of exerting Command and Control (C2) over a patients state (i.e., admitting, discharging, silencing alarms, changing the way an algorithm behaves.) These types of features must be at the foundation of the system, otherwise the entire system at risk. In our system, we are using DDS-Secure to help with these issues. | ||
| - | * Transport independent, the best transport is used for the communication link - Some of the links are wireless [[ddsf:public:guidebook:06_append:glossary:l:lan|LAN]], some are over wired high-seed networks, and others are over [[ddsf:public:guidebook:06_append:glossary:p:point-to-point|point-to-point]] "body area" [[ddsf:private:guidebook:06_append:glossary:w:wireless|wireless networks]]. Not everything is [[ddsf:public:guidebook:06_append:glossary:e:ethernet|Ethernet]] or [[ddsf:public:guidebook:06_append:glossary:i:ip]], therefore, we use a service which not tied to a specific transport allowing the right transport to be selected for the right purpose. This applies all the way along the communication pathway from the edge to the severs. | + | * Transport independent, the best transport is used for the communication link - Some of the links are wireless [[ddsf:public:guidebook:06_append:glossary:l:lan|LAN]], some are over wired high-seed networks, and others are over [[ddsf:public:guidebook:06_append:glossary:p:point-to-point|point-to-point]] "body area" [[ddsf:public:guidebook:06_append:glossary:w:wireless|wireless networks]]. Not everything is [[ddsf:public:guidebook:06_append:glossary:e:ethernet|Ethernet]] or [[ddsf:public:guidebook:06_append:glossary:i:ip]], therefore, we use a service which not tied to a specific transport allowing the right transport to be selected for the right purpose. This applies all the way along the communication pathway from the edge to the severs. |
| * Software defined domains and topics - Help shape the distribution of data, the virtual communication of which endpoints communicate with each other, also adding to the design architectures and the security and efficiency of the system. | * Software defined domains and topics - Help shape the distribution of data, the virtual communication of which endpoints communicate with each other, also adding to the design architectures and the security and efficiency of the system. | ||
ddsf/public/guidebook/03_user/02_health.1626292441.txt.gz · Last modified: 2021/07/14 15:54 by murphy
