Re: Best Approach Suggestions

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Jerry,

You can define a "linked server" on MS SQL Server that allows you to
basically hit tables on the i as if they were just another table of
the MS SQL Server.

You can also execute stored procedures on the "linked server".

HTH,
Charles


On Fri, Feb 19, 2010 at 2:51 PM,  <GKern@xxxxxxxxxxxxxxxx> wrote:
> I have a project on the horizon that will require the users to use an MS
> MS-SQL based system to enter/maintain data that has to be validated
> against the database on an i. If the edits are passed they will update the
> database on the i and the data will be passed to our Electronic Medical
> Record (EMR) application.
>
> The application on the MS box will be table driven and the "mostly" static
> data will be updated in batch weekly (or possibly nightly). I don't know
> much about the product but will attend a demo next week. The volatile data
> will need to be edited in real time against the i. I'm not sure what tools
> the MS box developer will have or what his skill set is so I want to know
> what options are available to me and anything else I might want to be
> aware of.
>
> My guess is that he will do calls to SQL stored procedures residing on the
> i that will edit and then return a response indicating if the i has
> accepted or reject the data.
>
> This product is a third party EMR application that specializes and manages
> oncology therapies and the key data (patient demographics, appointments
> etc) will need to be passed (via our i) tor our clinic wide EMR - hence
> the need to ensure any data entered/maintained in this oncology product
> passes our business logic/rules on the i before it can be sent to the EMR.
>
> Comments welcome.
>
> Thanks!
>
> Regards, Jerry
>
> Gerald Kern - IT Project Leader
> Lotus Notes/Domino Administrator
> IBM Certified RPG IV Developer
> The Toledo Clinic, Inc.
> 4235 Secor Road
> Toledo, OH 43623-4299
> Phone 419-479-5535
> gkern@xxxxxxxxxxxxxxxx
>
>
> This e-mail message, including any attachments, is for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information. Any unauthorized use, disclosure or distribution is
> prohibited. If you are not the intended recipient, please inform the
> sender by reply e-mail and destroy this and all copies of this message.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.