|
From: Peter Hutten-C. <ph...@SR...> - 2013-10-04 13:19:54
|
on the subject of bugs The only ones guaranteed to be fixed are the ones affecting conformance with OntarioMD specifications the rest is catch as catch can (about 300 or so fixed in 12_1 to date) In BC we (OCUS) STRONGLY encourage someone who is commissioning a bug fix or feature enhancement to ensure that the contract includes a requirement to commit it to the source so that it doesn't consume the resources of 30 OSP's trying to fix the same thing or leaving it unfixed. In Ontario that is good practice as well, although hopefully will soon become somewhat redundant with the institution of a tracability process that ensures everyone is running the latest stable release with everyone's bug fixes included. To whit if you are running a OntarioMD supported product you will be able to identify its build that will tie to a specific source code that is available. Bug fixes instituted by OSP A will be published in the repository and can be cherry picked for urgent upgrades to existing code and will be automatically included in the next official release within a reasonable time frame. ================ Peter Hutten-Czapski Haileybury Ontario "The attitude that ‘if rural people want these services they’ll have to come to the city to get them’ is simply not acceptable…” (Newbery, 1999) Before printing, think about the environment. Avant d' imprimer, pensez à l'environnement. On 3 October 2013 21:41, Earl Wertheimer <ea...@gm...> wrote: > John > > If you really consider this a bug, then you can log a report and wait > until it is fixed. > Then you will have the fix as part of your next upgrade. > > There is a grey area when determining whether something is a bug or just > needs improvement. > > Everyone here wants you to be happy with Oscar, but the people fixing > things also need to get paid (sometimes). > > Perhaps someone has already found and fixed the problem.... > > > > > On Thu, Oct 3, 2013 at 5:12 PM, Chris Sedergreen <cse...@gm...>wrote: > >> >> Hallo John, >> >> From the OSCAR Canada web sire: >> >> The eyeform is a highly modified interface designed for Ophthalmology and >> Optometry >> >> Looking at a screen shot on the web site this appears to be code >> modification of the original OSCAR software. Unless you're a super-geek you >> probably won't want to tackle this. >> >> But your enquiry does raise questions as to what we should expect from >> our service providers. If and OSP knows that there is a defect in the code >> for a specialty version I would think they should reasonably be expected to >> make you aware of this before signing up with them - especially if this is >> going to involve extra, unanticipated costs. (If they didn't know, then I >> suppose they cannot be faulted). >> >> Perhaps I'm wrong (reading too much into your remarks?), but I sense I'm >> detecting that you have a concern about your OSP's 'attitude'. It might be >> an idea to call around to other OSPs to see if they are willing to have a >> more compromising approach. >> >> Chris. >> >> >> >> >> >> On 03/10/2013 1:46 PM, John Stuart wrote: >> >> I am a new Oscar 12.1 user in BC using EyeForm. Whenever I try to print >> a consultation letter, consultation report, or an encounter report from an >> examination in the EF form, the data entered in “Current Presenting >> Issue/History” is listed at the bottom of the report as “Impression/Plan” >> instead of at the top as “Current History”. My OSP, OscarHost, tells me >> that this is a defect in EyeForm and I will have to pay them to correct it. >> Does anybody know of an easier fix for this?**** >> >> ** ** >> >> Thanks,**** >> >> ** ** >> >> John**** >> >> >> ------------------------------------------------------------------------------ >> October Webinars: Code for Performance >> Free Intel webinars can help you accelerate application performance. >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >> the latest Intel processors and coprocessors. See abstracts and register >http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk >> >> >> >> _______________________________________________ >> Oscarmcmaster-bc-users mailing lis...@li...://lists.sourceforge.net/lists/listinfo/oscarmcmaster-bc-users >> >> >> >> >> ------------------------------------------------------------------------------ >> October Webinars: Code for Performance >> Free Intel webinars can help you accelerate application performance. >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most >> from >> the latest Intel processors and coprocessors. See abstracts and register > >> >> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk >> _______________________________________________ >> Oscarmcmaster-bc-users mailing list >> Osc...@li... >> https://lists.sourceforge.net/lists/listinfo/oscarmcmaster-bc-users >> >> > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk > _______________________________________________ > Oscarmcmaster-bc-users mailing list > Osc...@li... > https://lists.sourceforge.net/lists/listinfo/oscarmcmaster-bc-users > > |
