I don't know much about this, but I think that my requirements with regard to schema are exceedingly limited. All I need is enough of the database "structure" to be able to piece the individual data elements back into a format that is useful for export. From then on, all I would be interested in is "My" data, in its new database.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hugh Leslie Sent: Monday, 23 October 2006 12:24 PM To: 'General Practice Computing Group Talk' Subject: RE: [GPCG_TALK] SQL schema for billing Is there an issue of copyright here? I am not sure if HCN or Medtech would be happy for their exact schema to be reused in any other arena even if it is open source... Data is one thing - you own the data, but I think the exact schema will be copyright. __________________________________ Dr Hugh Leslie MBBS, Dip. Obs. RACOG, FRACGP, FACHI M: 0404 033 767 E: [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Chris Tansell > Sent: Monday, 23 October 2006 12:48 PM > To: 'General Practice Computing Group Talk' > Subject: RE: [GPCG_TALK] SQL schema for billing > > Does anyone know if this is possible with a MedTech32 database? > > Is it possible to migrate the data so simply? > > Cheers, > > Chris. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Horst Herb > Sent: Sunday, 22 October 2006 4:13 PM > To: General Practice Computing Group Talk > Subject: Re: [GPCG_TALK] SQL schema for billing > > On Sunday 22 October 2006 14:44, Richard Hosking wrote: > > as Pracsoft to a rails DB. If the DB schema is known this should be > > possible using a Ruby script. > > The db schema of pracsoft is known and quite simple. > On Linux, you can use "mdbtools" to migrate the whole prasoft database > to postgres or mysql with a single command > > (On Debian / Ubuntu you can install mdbtools with "apt-get install > mdbtools", then read the man file, copy the pracsoft Access database > file onto your Linux box, and you are done in minutes. > > Make sure you use the switches for "safe names" = replacing all spaces > with underscores in table and column names etc > > Once you have exported the database to postgres, you can use tools > like > pgadmin3 to explore the database schema (apt-get install pgadmin3 ...) > > Horst > _______________________________________________ > Gpcg_talk mailing list > [email protected] > http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk > > _______________________________________________ > Gpcg_talk mailing list > [email protected] > http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk > > __________ NOD32 1.1825 (20061022) Information __________ > > This message was checked by NOD32 antivirus system. > http://www.eset.com > > _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
