| Denzil Pinto's profileTheBuzzPhotosBlogLists |  Tools  Help |
TheBuzzHL7
Windows Communication Foundation
August 16 Message Logging, Tracing - Log Entire messageInorder to log messages do the following: This is for logging the entire message
< system.serviceModel>< diagnostics>< messageLogging logEntireMessage="true"/></ diagnostics></ system.serviceModel>< system.diagnostics>< sources>< source name="System.ServiceModel.MessageLogging" switchValue="Verbose">< listeners>< add name="tracing" type="System.Diagnostics.XmlWriterTraceListener" initializeData="c:\trace\traceFile.svclog"/></ listeners></ source></ sources></ system.diagnostics>ChannelsIn order to exchange messages between a client and service a channel is required.
The channel is created by the client which specifies the address where the service is located and the type of channel to create.
When a client creates a channel and establishes a connection with the service, the service has to accept the clients request to open the channel before they can start exchanging messages. Messaging PatternsThere are three messaging patterns that can be used to exchange messages
1. Simplex
2. Duplex
3. Request-Reply
Simplex - One-way communication, the client is not expecting a response.
Duplex - Two-way communication, the client in this messaging pattern is not waiting for a response, the communication is done freely.
Request-Reply : In this pattern the client sends a request and waits for a reply.
August 15 Contracts - Talk about the WCF architecture
A Data contract specifies the data that will be exchanged by the service. A message contract specifies the SOAP messages that will be sent and received by the service. A Service Contract in simple terms specifies the messages and their datatypes, the location of the service, and the protocols. For policy and binding just a simple example security protocol. The policy needs to be satisfied before the services can communicate Most of the times a data contract is sufficient but defining a message contract gives you more control.
April 06 HL7 dataHealthCare data is created as a result of an event. An Event triggers specific healthcare data that needs to flow between systems. HL7 is a standard that can be used to communicate healthcare data between systems.
A patient registeration at a hospital will trigger an event.
A patient admission will trigger another event.
Any lab tests will trigger one type and a return of lab results will trigger another event. These events are identified by a unique 3 character code.
|
|||||||||||||||||||||||||||
|
|
