Combining Cloud Computing, Client-Server In Addition To New Pub/Sub Mesh Node Network Architectures (Part Ane Of 2)
There are at to the lowest degree 3 key architectures for deploying wellness information technology software programs in addition to exchanging patient information:
- Cloud computing
- Client server
- Publish/subscribe mesh node networks.
Cloud Computing Architecture Described
Here's a Definition of the cloud computing architecture that I believe captures its essence: Cloud computing architectures shop software programs in addition to information inward servers that are accessed over the Internet via services (e.g., software equally a service, SaaS); spider web browsers furnish destination users an online interface to those services. The servers—along alongside the software in addition to centralized databases they contain—may hold upward owned in addition to managed past times third-party vendors (public cloud), past times the destination user's organisation (private cloud), or past times both (hybrid cloud). In other words, typical cloud computing enables applications to hold upward accessed online from a Web browser, piece the software in addition to information are stored on remote servers. See this link for a depiction of how CPS nodes furnish a simple, low-cost, secure way to commutation wellness data.
In add-on to their asynchronous pub/sub functionality (described above), CPS nodes have got other critical capabilities including:
- Data transformation
- Universal translation
- Composite reporting.
Data Transformation Capabilities
CPS nodes usage their extensive information transformation capabilities when information structures have got to hold upward modified to allow disparate databases to commutation their data. This happens when, for example, the databases have got (a) dissimilar table in addition to field names, (e.g., 1 database may usage the champaign "birth_date" in addition to simply about other "dob" or (b) dissimilar information formats/syntax, e.g., whether the nascence information is month/day/year (as inward U.S.) or day/month/year (as inward Europe), equally good equally how many digits or characters are used inward the date.
One way to bargain alongside the number of exchanging information betwixt incompatible databases is forcing everyone to usage the same information standard. One such method is transforming all information to As I discussed at this link, 2 advantages of the CPS information files over XML are: (1) they are easily 1000% to 2000% (10 to twenty times) smaller than XML files containing the same information in addition to (2) they are much simpler in addition to to a greater extent than efficient to procedure (i.e., parse in addition to render) than XML.
As the information are existence sent to the CPS information file, the publishing node transforms them depending on the information format needed past times each subscribing node. The publisher so ships the transformed information to the subscribing node. The transformation procedure requires that the publisher node hold upward notified inward advance equally to the information transformations required past times each subscribing node. This notification procedure tin spill out during when a subscribing node registers alongside a publishing node, or upon a subscribing node's asking for information from the publishing node.
Universal Translation Capabilities
CPS nodes usage their universal translation capabilities when publishers usage a dissimilar linguistic communication or damage than their subscribers. This is most probable to spill out when people inward loosely-coupled professional person in addition to social networks portion information; that is, when various groups of individuals commutation information from various information sources. One such instance is the vast variety of people who volition commutation a keen variety of information across a national wellness information network. Sometimes linguistic communication translation is necessary (e.g., English linguistic communication to Spanish), which is fairly straightforward. Other times dissimilar people usage dissimilar damage (their local terminology standards) to refer to the same concept (thing or idea), which tin hold upward a complex problem.
One mutual strategy used to bargain alongside complex terminology problems is to discard local terminology standards past times forcing everyone to adopt the same global terminology standards. This is done past times agreeing on 1 gear upward of damage (semantics) for a especial thing. While such global standards for health-related damage tin foster widespread communications betwixt people from dissimilar regions, organizations in addition to disciplines, in that location is a serious downside to eliminating the local standards people rely upon; the occupation is the loss of of import information due to reduced semantic precision in addition to nuance.
Take, for example, the term "high blood pressure;" in that location are 126 dissimilar damage referring to this concept of elevated blood pressure level levels. These damage include "malignant hypertension," which refers to really high blood pressure level alongside swelling of the optic nervus behind the eye; it's a status unremarkably accompanied past times other organ impairment such equally pith failure, kidney failure, in addition to hypertensive encephalopathy. "Pregnancy-induced hypertension," on the other hand, is when blood pressure level rises during pregnancy (also called toxemia or preeclampsia). These are really dissimilar types of hypertension. So, piece referring to a person's status using a global standard term such equally "hypertension" clearly conveys that the someone has high blood pressure, the standardized term loses of import details constitute inward the to a greater extent than detailed local standard terms. These lost details, inward turn, could really good touching on handling decisions in addition to outcomes. So, in that location is a proficient argue to have got multiple damage that refer to the same health-related concept.
An wages of the nodes' universal translation capabilities, therefore, is that they enable end-users to boot the bucket on existing local standards, back upward the development of those standards, in addition to usage the information translation described higher upward to ensure everyone gets the information needed using the damage they postulate in addition to understand. In a node network, this tin hold upward accomplished inward a way similar to information transformation. But instead of having the publishing node transform the data, it replaces specific damage alongside the alternate damage required past times the subscribing nodes.
Composite Reports
The nodes tin likewise generate composite reports that are comprised of information sent from multiple publisher nodes to a unmarried subscriber node. The subscriber node takes all that information from multiple sources in addition to combines it into a unmarried integrated patient wellness study that is tailored to the needs of the individual.
For example, let's enjoin a primary attention Dr. (PCP) wants to boot the bucket on rails of the handling a patient is receiving from several provider specialists. The PCP's node, which serves equally the subscriber, would ship a asking for surely information from all the patient's specialists. Upon receipt of the information request, the specialists' nodes, which serve equally the publishers, holler back the requested information from their dissimilar electronic wellness tape databases, transform in addition to interpret the information equally necessary, in addition to so ship the information automatically to the PCP's node. The PCP's node so incorporates the information into a composite study tailored to the PCP's needs in addition to preferences, in addition to presents the study on concealment for the PCP to view. The PCP's subscriber node could likewise hold upward instructed to asking information from the patient's node connected to his/her personal wellness tape and, upon receipt, add together the information into the same report. Likewise, a patient node could exercise composite reports inward a similar mode from information sent past times multiple provider nodes.
So, which architecture is best—cloud, client-server, the new pub/sub node network, or a combined solution that embraces all three? I fence that it's the latter, whereby the benefits of each architecture are realized inward dissimilar usage cases.
In my side past times side post, I will share my thoughts nearly this multifaceted solution past times presenting possible usage cases.
Related posts:
- Combining Cloud Computing, Client-Server in addition to Novel Pub/Sub Mesh Node Network Architectures (Part 2 of 2)
- The force for ‘push’ engineering for the NHIN
- A Novel Way for Everyone inward the Nation to Exchange Health Data Simply, Inexpensively in addition to Securely
- Simple, Low-Cost, Secure Health Data Exchange
- Who should Own a Patient’s Health Data, Where should they hold upward Stored, in addition to How should they hold upward Exchanged (Part 1 of 2)
- Who should Own a Patient’s Health Data, Where should they hold upward Stored, in addition to How should they hold upward Exchanged (Part 2 of 2)
- Health IT: Comparing Cloud Computing in addition to Desktop Applications (Part 1)
- Health IT: Comparing Cloud Computing in addition to Desktop Applications (Part 2)
- Health IT: Comparing Cloud Computing in addition to Desktop Applications (Part 3)
- Dueling Data Formats
- Knowledge, Standards in addition to the Healthcare Crisis: Part 6
- Introducing our disruptive CP Split technology