I have a customer that is implementing a 270/271 solution with CMS. After examining the CMS companion guides they require you to use TCPIP Socet Streaming to send/receive data. I was looking for anyone that has dome this with them before and some pointers on how to implement this using BTS06 and HIPAA 3.3. Creating the 270 is not a real concern, I'm more intersted in how some of you integrated in the Socket streaming with CMS. I assume some custome programming with System.NET.Sockets but is this advisable let's say from an orchestration? We have the leased line ealready set up (extranet) From the CMS companion guide: 4.1 Real Time Communications Transport Protocol Communications through the Extranet to the CMS data center will be via the TCP/IP streaming socket protocol. Trading Partners can submit multiple 270 transactions without waiting for a response before triggering the next 270. Trading partners must ensure that the session remains connected until all responses are received. Each submitted transmission shall contain one 270 transaction with only one ISA and IEA segment, along with a transmission wrapper around the 270 transaction. The transmission wrapper Header/Trailer has no Segment ID associated with it and requires the length of the transaction message. There will be no handshake after the connection is accepted with the first submitted transmission. Outbound response transactions will have the same format transmission wrapper. The response to the submitter will be returned in the same session in which the 270 was submitted. -- Michael Krok President Mallard Solutions LLC Microsoft Certified Partner -- Michael Krok President Mallard Solutions LLC Microsoft Certified Partner
Sounds like a Socket adapter would be the answer. There is an example here. http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=D3AC121C-8963-4735-B5E1-FC83B02F57C1 Greg "Michael Krok" <TheDuck@newsgroup.nospam> wrote in message news:71A0679D-AE1D-4204-9507-887B9163BEEF@microsoft.com... >I have a customer that is implementing a 270/271 solution with CMS. After > examining the CMS companion guides they require you to use TCPIP Socet > Streaming to send/receive data. I was looking for anyone that has dome > this > with them before and some pointers on how to implement this using BTS06 > and > HIPAA 3.3. Creating the 270 is not a real concern, I'm more intersted in > how > some of you integrated in the Socket streaming with CMS. I assume some > custome programming with System.NET.Sockets but is this advisable let's > say > from an orchestration? We have the leased line ealready set up (extranet) > > From the CMS companion guide: > 4.1 > Real Time Communications Transport Protocol Communications through the > Extranet to the CMS data center will be via the TCP/IP streaming socket > protocol. Trading Partners can submit multiple 270 transactions without > waiting for a response before triggering the next 270. Trading partners > must > ensure that the session remains connected until all responses are > received. > Each submitted transmission shall contain one 270 transaction with only > one > ISA and IEA segment, along with a transmission wrapper around the 270 > transaction. The transmission wrapper Header/Trailer has no Segment ID > associated with it and requires the length of the transaction message. > There > will be no handshake after the connection is accepted with the first > submitted transmission. > > Outbound response transactions will have the same format transmission > wrapper. The response to the submitter will be returned in the same > session > in which the 270 was submitted. > -- > Michael Krok > President > Mallard Solutions LLC > Microsoft Certified Partner > -- > Michael Krok > President > Mallard Solutions LLC > Microsoft Certified Partner
Thanks Greg - ReadMe says it requires BizTalk 2004 - hope it works out ok with 2006, it should -- Michael Krok President Mallard Solutions LLC Microsoft Certified Partner "Greg Forsythe" wrote: > Sounds like a Socket adapter would be the answer. > There is an example here. > http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=D3AC121C-8963-4735-B5E1-FC83B02F57C1 > > Greg > > "Michael Krok" <TheDuck@newsgroup.nospam> wrote in message > news:71A0679D-AE1D-4204-9507-887B9163BEEF@microsoft.com... > >I have a customer that is implementing a 270/271 solution with CMS. After > > examining the CMS companion guides they require you to use TCPIP Socet > > Streaming to send/receive data. I was looking for anyone that has dome > > this > > with them before and some pointers on how to implement this using BTS06 > > and > > HIPAA 3.3. Creating the 270 is not a real concern, I'm more intersted in > > how > > some of you integrated in the Socket streaming with CMS. I assume some > > custome programming with System.NET.Sockets but is this advisable let's > > say > > from an orchestration? We have the leased line ealready set up (extranet) > > > > From the CMS companion guide: > > 4.1 > > Real Time Communications Transport Protocol Communications through the > > Extranet to the CMS data center will be via the TCP/IP streaming socket > > protocol. Trading Partners can submit multiple 270 transactions without > > waiting for a response before triggering the next 270. Trading partners > > must > > ensure that the session remains connected until all responses are > > received. > > Each submitted transmission shall contain one 270 transaction with only > > one > > ISA and IEA segment, along with a transmission wrapper around the 270 > > transaction. The transmission wrapper Header/Trailer has no Segment ID > > associated with it and requires the length of the transaction message. > > There > > will be no handshake after the connection is accepted with the first > > submitted transmission. > > > > Outbound response transactions will have the same format transmission > > wrapper. The response to the submitter will be returned in the same > > session > > in which the 270 was submitted. > > -- > > Michael Krok > > President > > Mallard Solutions LLC > > Microsoft Certified Partner > > -- > > Michael Krok > > President > > Mallard Solutions LLC > > Microsoft Certified Partner > > >
