...
I have included a very rough diagram of these components. Please let me know what you think and if I have captured this correctly. I'm sure I have forgotten something or mis-represented something. (Ryan)
Two Diagrams
What follows are two diagrams of the central node. After some discussions, we realize that they are describing the same problem, but at two levels of generality. Ryan's shows the situation "in general". Logging and authentication for the "Main Line HL7 Data Flows" is handled by exactly the same machinery as the "pass through registry exposure" calls. Mark's diagram shows a concrete architecture conforms to Ryan's general picture. By saying that "pass through registry exposure" goes through a pass-thru apache, we are in essense limiting the amount of authentication and transformations that happen between what is exposed (message m1 sent to FR.exposed), vs what is presented to the FR (message m1')
The idea is that if you imagine more than can be accomplished by the concrete architecture of Mark's diagram, then please bring that use case forward so we can understand it
Mark's diagram
The diagram below shows the internals of the Core Node.
...
At the bottom is the full-on HL7 pipeline V2 messages arrive from edge nodes via LLP. Are remembered forever in the Raw message store. A pre-processor attacks them to normalize them. (Note: In the common case, the arriving messages are already "perfect"! But, when the edge node had operated disc-connected, there may be issues. In any case, we are ready to do hard work for mal-conformant edgenodes.) (NOTE: I assume that the LLP reader implements some simple certificate-based security.)
Finally, the normalized messages remembered, and presented to the SHR.
...