Re: [Care2002-developers] Insurance Module: Care2x and WebErp
Hello Steve! I have some problems with Weberp. I want to integrate weberp and care2x, I mean when I login user and pass into care2x, it auto send user and pass to weberp. And in weberp it doesn't need to login. Could you help me? I want to know idea and how can I code it? So far, I want to get data into care2x (prices, services, items,...related discharge patient) send to weberp (weberp take, process order and show results). Thank you very much. Gwen Lee, On Jul 23, 2007 5:25 PM, <[EMAIL PROTECTED]> wrote: > You asked ;) Only a system knows itself. So, weberp knows itself and > Care2x knows itself. They don't know each other, they don't want to know > each other and they don't want to have to change every time the other does. > Therefore > > 1) A weberp API > > 2) A Care2x API > > 3) A go between that connects the two based on it communicating between > them > > APIs that do everything under the sun are unnecessary. Parts of them can > be built at a time. In your case you need some API functionality for certain > item, item category, price list and payables (not sure about that one?). It > must be realized the exact functionality needed between the two. For > instance, will Care2x need to update price lists? Will it only need to > retrieve prices from price lists in weberp? Just an example. > > The good news about APIs instead of integrating is > > 1) Each system can provide that API for any other system. So, the Care2x > API is "basically" ready for any ERP. It just does what it's supposed to do > for its system. It knows it's "business" logic, it knows its database. > > 2) It does not affect the upgrading of each system. Each system is still > fully contained as its own project without obscuring the other's code. Each > project community knows its own project. Integrating means weberp code would > be within Care2x code and affect either all future Care2x releases or, if > not incorporated for everyone, then your customized version. Good luck with > upgrading and support forevermore in the latter case :O > > 3) Most/All licenses will allow this way. The APIs are part of them. The > connectors are separate works that could but don't need to be included in > one or both. Care2x does not touch weberp and weberp does not touch Care2x. > They remain identifiable, separate works. This is to the best of my > knowledge so confirm for yourself but that would seem to be the > understanding of many and it certainly makes perfect sense to me. In this > way, neither could ever be thought to be works based on the other. So, you > end up with compatibility between licenses without interference and between > systems with even the same license without any ramifications. Just don't > burn a disk with all on it and go distributing it to others if either > license has any stipulation about being on the same media. That's a silly > stipulation that I believe newer versions of licenses are correcting. > > An API for Care2x takes away 1/3 of the work in > "integrating"/interfacing/connecting it to other systems. A great > encouragement for other systems to communicate with it. However, it needs to > be well documented. Functions, parameters and how to use. > > It will be harder than simple integration but the benefits are great now > and for all time which means integration will not make sense and this way > does. From the angle of each API one must only consider what needs to be > obtained and supplied to the connector in the general sense. If that doesn't > conform to the other system, tough. Let the connector work as the go > between. > > The Care2x end could avoid the API if you know Care2x and must get the > work done for one particular customer but I would suggest doing it in a way > that can be extracted into a Care2x API in the future. Soon you and/or > someone else will need similar. > > I would suggest using simple functions in all. A vehicle such as xml, hl7, > etc. is only a vehicle. They have nothing to do with the logic so why > complicate matters. > > Steve > > -Original Message- > From: [EMAIL PROTECTED] [ > *mailto:[EMAIL PROTECTED]<[EMAIL PROTECTED]>] > On Behalf Of Absar Ali > Sent: Sunday, July 22, 2007 12:48 PM > To: care2002-developers@lists.sourceforge.net > Subject: [Care2002-developers] Insurance Module: Care2x and WebErp > Hi All, > I am working on patient insurance module which is integreated with WebERP, > I > have to send and get the following data from WebERP. > 1. Price List. > 2. Items Category(Service Type in Care2x, like ENT, Cardiaology, > Pathology, > etc) > 3. Items(Which is called services in Care2x). > 4. send payable data of insurance companies to General Ledger > for this i have to create another connect. > suggest what should i do. > > Regards, > Absar Ali > +966566123813 > Senior Support Consultant. > _ > * > http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_pcmag_0507 > *
Re: [Care2002-developers] Insurance Module: Care2x and WebErp
Hello Robert! You had send and get data from WebERP. I want to know how can I code it? thank you very much Gwen Lee, On Jul 23, 2007 1:40 PM, Robert Meggle < [EMAIL PROTECTED]> wrote: > Hello Ali, > > That's sounds interesting, really nice work! > > > I am working on patient insurance module which is integreated with > WebERP, > > That's an idea what had a discussion topic some days ago here in the > developer's list. I would be really interested how your integration > strategy > is now realised and how it could be adapted. > > > I have to send and get the following data from WebERP. > > > > 1. Price List. > > 2. Items Category(Service Type in Care2x, like ENT, Cardiaology, > > Pathology, > > etc) > > 3. Items(Which is called services in Care2x). > > 4. send payable data of insurance companies to General Ledger > > > > for this i have to create another connect. > > Here I would suggest that there should be an interface on a more abstract > layer. I had suggested some strategies to the webERP developers list and > Tim > Schonfied answered to my question. I asked about possibilities to > integrate > XML interfaces to webERP exactly for your requirement of accounting > x-change. The aim would be not to integrate an interface to exactly one > ERP > sytem, the aim should be to integrate an accounting interface to care2x > itself that ERP's could connect care2x. :-) > > Can you show us litte bit more of your realisation or conception? > > Robert > > > > > suggest what should i do. > > > > > > Regards, > > Absar Ali > > +966566123813 > > Senior Support Consultant. > > > > _ > > http://imagine-windowslive.com/hotmail/?locale=en- > > us&ocid=TXT_TAGHM_migration_HM_mini_pcmag_0507 > > > > > > > - > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > ___ > > Care2002-developers mailing list > > Care2002-developers@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/care2002-developers > > > - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ___ > Care2002-developers mailing list > Care2002-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/care2002-developers > -- Ly Kim Quyen, Researcher, Department of Knowledge Engineeing IOIT-HCM/VAST - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Care2002-developers mailing list Care2002-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/care2002-developers
Re: [Care2002-developers] Insurance Module: Care2x and WebErp
Hello Steve! I have some problems with Weberp. I want to integrate weberp and care2x, I mean when I login user and pass into care2x, it auto send user and pass to weberp. And in weberp it doesn't need to login. Could you help me? I want to know idea and how can I code it? So far, I want to get data into care2x (prices, services, items,...related discharge patient) send to weberp (weberp take, process order and show results). Thank you very much. Gwen Lee, On Jul 24, 2007 11:12 PM, Steve <[EMAIL PROTECTED]> wrote: > I can help on the ERP side. Contact me anytime if you wish. > > Steve > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Absar Ali > Sent: Tuesday, July 24, 2007 12:09 PM > To: care2002-developers@lists.sourceforge.net > Subject: Re: [Care2002-developers] Insurance Module: Care2x and WebErp > > Hi All, > > Thnk for such a perfect answer, > i have three databases running > 1. Care2x > 2. WebERP > 3. Insurance > > I have to send data from my insurance module to Care2x and WebERP, that > means all three Portals will share the with each other. > what i have done is, i created seprate classes for making a connection to > WebERP and Insurance module. > > I Know its not the right way to do just for the time being insted of brain > storming in APIs of Care2x and WebERP(spending more time in analysis > rather > then development). > > > Regards, > Absar Ali > +966566123813 > Senior Support Consultant. > > > >From: [EMAIL PROTECTED] > >Reply-To: care2002-developers@lists.sourceforge.net > >To: care2002-developers@lists.sourceforge.net > >Subject: Re: [Care2002-developers] Insurance Module: Care2x and WebErp > >Date: Mon, 23 Jul 2007 03:25:15 -0700 > > > > > >You asked ;) Only a system knows itself. So, weberp knows itself and > Care2x > > >knows itself. They don't know each other, they don't want to know each > >other and they don't want to have to change every time the other does. > >Therefore > > > >1) A weberp API > > > >2) A Care2x API > > > >3) A go between that connects the two based on it communicating between > >them > > > >APIs that do everything under the sun are unnecessary. Parts of them can > be > > >built at a time. In your case you need some API functionality for certain > >item, item category, price list and payables (not sure about that one?). > It > > >must be realized the exact functionality needed between the two. For > >instance, will Care2x need to update price lists? Will it only need to > >retrieve prices from price lists in weberp? Just an example. > > > >The good news about APIs instead of integrating is > > > >1) Each system can provide that API for any other system. So, the Care2x > >API is "basically" ready for any ERP. It just does what it's supposed to > do > > >for its system. It knows it's "business" logic, it knows its database. > > > >2) It does not affect the upgrading of each system. Each system is still > >fully contained as its own project without obscuring the other's code. > Each > > >project community knows its own project. Integrating means weberp code > >would be within Care2x code and affect either all future Care2x releases > >or, if not incorporated for everyone, then your customized version. Good > >luck with upgrading and support forevermore in the latter case :O > > > >3) Most/All licenses will allow this way. The APIs are part of them. The > >connectors are separate works that could but don't need to be included in > >one or both. Care2x does not touch weberp and weberp does not touch > Care2x. > > >They remain identifiable, separate works. This is to the best of my > >knowledge so confirm for yourself but that would seem to be the > >understanding of many and it certainly makes perfect sense to me. In this > >way, neither could ever be thought to be works based on the other. So, > you > >end up with compatibility between licenses without interference and > between > > >systems with even the same license without any ramifications. Just don't > >burn a disk with all on it and go distributing it to others if either > >license has any stipulation about being on the same media. That's a silly > >stipulation that I believe newer versions of licenses are correcting. > > > >An API for Care2x takes away 1/3 of the work in > >"integrating"/interfacing/connecting it to other systems. A great > >encouragement for other systems to communicate with it. However, it needs > >to be well documented. Functions, parameters and how to use. > > > >It will be harder than simple integration but the benefits are great now > >and for all time which means integration will not make sense and this way > >does. From the angle of each API one must only consider what needs to be > >obtained and supplied to the connector in the general sense. If that > >doesn't conform to the other system, tough. Let the connector work as the > >go between. > > > >The Care2x end could avoid the API if you know Care2x and must get the > work > > >done f
