Just had an oddity on my Galaxy S3 phone – I had no data connectivity over the air!
I tried the typical restart and disable/enable Airplane mode with no avail.
How I fixed it (some steps may be optional/redundant – I don’t know):
- Update PRL – Settings -> More -> System Update -> Update PRL
- disable WiFi
- disable phone data – Settings -> Connection -> Data Usage -> Mobile Data
- enter Airplane mode
(in other words – shut off everything)
- power cycle the device to force a full reboot
- come out of Airplane mode
- re-enable phone data
Whew – see the 4G/LTE icon…
I left WiFi disabled because there were some comments that WiFi coming in and going out may have a bug in the new Android (I’m using KitKat 4.4.2).
From an interesting article in Science Magazine – Trio of big black holes spotted in galaxy smashup, one sentence jumped out at me…
…three supermassive black holes orbiting close to one another, two of them just a few hundred light-years apart.
Golly – JUST a few hundred light-years apart.
Otherwise the item is interesting because this would be a great source of gravitational waves. Harnessing a small or quantum singularity and vibrating that may be more useful, but until we figure that out, we can watch these supermassive babies.
My new job is using SQL Server (rather than SAP-HANA or Sybase!!) as a database engine. During a manual install of the product I’m working on I stumbled over a couple small changes with 2012 that had changed since SQL Server 2005 (and even version 6.5!!)
- Authentication mode
‘Out of the box’ – the server defaults to only ‘Windows Authentication’.
However user ‘sa’ is (obviously) not a windows user.
Easy change: Server Properties – Security – Authentication – select both SQL Server and Windows Authentication.
- User ‘sa’
In Ye Olde Days – the password was blank.
The new recommendation is ‘Password123′.
(yes – I did remember that when I found it online – just slipped my puppy-brain).
- The CLR engine (for .NET objects) has to be enabled before it’s used.
Yes – I remembered that one too when I found it online…
The PowerBuilder group on FaceBook pointed to the open source project “EncounterPRO EMR Clinical Groupware for Pediatrics and Primary Care” at encounterpro.org. This project uses a mix of C# and our beloved PowerBuilder.
PowerBuilder 11.5 is used for both the client application UI and server components.
This seems to be an open source version of a proprietary product – don’t ask me how that all works and the relationships.
This open source version is still in development, there don’t seem to be any installations yet. The However the project is addressing the common issues in both the client UI and EMR server-side that I am familiar with. I will be giving this a look, see how it stacks up to ‘openMRS‘ and whether I should be spending my spare time here instead.
Open MRS has the advantage of an installed “customer” base with a worldwide mission. This ‘EncounterPRO’ project has a strong focus for the physician/nurse encounter workflow – which I see as more important the back-end services. From skimming the docs it seems to be using a more general workflow engine, which matches my general approach to problems. Additionally, using PowerBuilder just makes the cake that much tastier!
Maybe mobilize this with Appeon? Version 2.0 is now in beta and it looks good.
A couple people have asked what I have been doing lately. Fortunately I have been putting my talents for good rather than evil (even though evil is so tempting, and they have cookies).
I am becoming familiar (and hopefully soon being useful) on the open source electronic medical record (EMR) software “OpenMRS” (openmrs.org). This project combines my interests in EMR software (and data models) with my desire to make a real contribution for efficient and effective delivery of healthcare. Just in Kenya this software is used in over 50 clinics supporting hundreds of thousands of patients.
Fortunately this system is using tools I am familiar with – code is Java, GIT for version control, and JIRA for issues and scrum. I am still getting familiar with the codebase and will soon have the confidence to take an issue from JIRA or even propose some new functionality (like a remote ‘visiting nurse’ tablet application).