Parallel network architecture for aggregate data routing
Network architectures are interfaced with diverse inputs like a hub with multiple spokes. A portion of these input are further interfaced as limited outputs. The inputs can be from wholly different users streaming unrelated data in different protocols. HL7 ADTs in these inputs can control network configuration, culling or screening output to communications that match user parameters. Network architectures can aggregate and enhance information that matches from among these inputs, including information across protocols such as HL7. Such information can be provided and stored back to other sources so as to add to or correct wide area data stores. All communications can be provided in real-time and with manageable volumes that do not fatigue users and better manage network resources.
1. A network connected between a plurality of parallel streams and users to condition and route the streams, the network comprising:
a protocol interface connected to the plurality of streams, wherein the plurality of streams operate on different protocols and include at least one Health Level 7 (HL7) Admit Discharge Transfer message (ADT) stream, wherein the protocol interface is configured for different protocols including HL7;
an intake interface configured to receive parameters for network operation on the plurality of streams from a plurality of users separate from the plurality of streams; and
a processor and memory coupled to the intake interface and protocol interface, wherein the memory includes instructions that when executed by the processor, cause the processor to,
limit flow of the plurality of streams to a receiving user of the plurality users to only an HL7 ADT or a portion of the HL7 ADT, wherein the HL7 ADT or the portion of the HL7 ADT complies with the parameters for network operation for the receiving user, wherein the limiting is executed in real-time with the streams.
2. The network of claim 1 , wherein the instructions further cause the processor to,
format the HL7 ADT or the portion of the HL7 ADT in appearance and/or timing based on the parameters for network operation for the receiving user.
3. The network of claim 1 , wherein the instructions further cause the processor to,
combine information only from the parameters for network operation for the receiving user into the HL7 ADT or the portion of the HL7 ADT.
4. The network of claim 1 , wherein the HL7 ADT or the portion of the HL7 ADT complies with the parameters when a patient identity in the parameters matches a patient identity in the HL7 ADT.
5. The network of claim 1 , wherein the plurality of streams are controlled and operated by different entities in different locations.
6. The network of claim 1 , wherein the instructions further cause the processor to,
dispose of all non-HL7 ADT information from the streams.
7. The network of claim 1 , wherein instructions further cause the processor to,
aggregate information from the parameters into HL7 information from the streams when the information from the parameters corresponds to the HL7 information from the streams.
8. The network of claim 1 , wherein instructions further cause the processor to,
write information from the parameters to a data source of at least one of the streams for storage in the data source, wherein the information from the parameters includes information not previously stored in the data source.
9. The network of claim 8 , wherein the data source is a regional exchange networked and storing data among several providers.
10. The network of claim 1 , wherein the instructions further cause the processor to,
dispose of errors and duplicate information in the HL7 ADT or the portion of the HL7 ADT.
11. The network of claim 1 , wherein the instructions further cause the processor to,
add additional information not received from the plurality of streams to the flow to the receiving user.
12. A network connected between a plurality of parallel streams and users to enhance the streams, the network comprising:
a protocol interface connected to the plurality of streams, wherein the plurality of streams operate on different protocols and include at least one Health Level 7 (HL7) Admit Discharge Transfer message (ADT) stream, wherein the protocol interface is configured for different protocols including HL7;
an intake interface configured to receive parameters for network operation on the plurality of streams from a plurality of users separate from the plurality of streams; and
a processor and memory coupled to the intake interface and protocol interface, wherein the memory includes instructions that when executed by the processor, cause the processor to,
write patient-identifying information associated with a patient from the parameters to a data source of at least one of the streams for storage in the data source, wherein the information from the parameters includes information not previously stored in the data source.
13. The network of claim 12 , wherein the data source is a regional exchange networked and storing data among several providers.
14. The network of claim 12 , wherein the instructions further cause the processor to,
limit flow of the plurality of streams to a receiving user of the plurality users to only an HL7 ADT or a portion of the HL7 ADT, wherein the HL7 ADT or the portion of the HL7 ADT complies with the parameters for network operation for the receiving user, wherein the limiting is executed in real-time with the streams.
15. The network of claim 14 , wherein the instructions further cause the processor to,
format the HL7 ADT or the portion of the HL7 ADT in appearance and/or timing based on the parameters for network operation for the receiving user.
16. The network of claim 14 , wherein the instructions further cause the processor to,
combine information only from the parameters for network operation for the receiving user into the HL7 ADT or the portion of the HL7 ADT.
17. The network of claim 14 , wherein the HL7 ADT or the portion of the HL7 ADT complies with the parameters when a patient identity in the parameters matches a patient identity in the HL7 ADT.
18. The network of claim 14 , wherein the instructions further cause the processor to,
dispose of all non-HL7 ADT information from the streams.
19. The network of claim 12 , wherein the plurality of streams are controlled and operated by different entities in different locations.
20. A network, comprising:
a protocol interface connected to receive a plurality of streams from a plurality of sources including hospitals, wherein the plurality of streams are configured using different communication protocols and include at least one Health Level 7 (HL7) Admit Discharge Transfer message (ADT) stream, wherein the protocol interface is configured to accept different protocols including HL7;
an intake interface configured to receive at least one parameter relating to events and/or information on the plurality of streams from each of a plurality of users separate from the plurality of streams; and
a processor and memory coupled to the intake interface and protocol interface, wherein the memory includes instructions that when executed by the processor, cause the processor to,
limit flow of the plurality of streams in real time to a receiving user of the plurality users to only at least a portion of the HL7 ADT, wherein the at least a portion of the HL7 ADT complies with the at least one parameter for the receiving user.
21. The network of claim 20 , wherein the at least one parameter limits the plurality of streams to those streams that only include a particular healthcare patient that has an issue relating to the field of practice of the receiving user.
22. The network of claim 20 , wherein the instructions further cause the processor to,
further limit flow of the plurality of streams based on patient-identifying information from a roster maintained in the memory that includes a plurality of client parameters.