At PokeCircle we’re focused on a truly social vision.
When we saw the huge impact Pokemon Go had on our families, friends, and neighbors with its July 2016 launch, we took notice.
We believe Pokemon Go paves the way to build renewed social interaction; something that has steadily declined in today’s fast moving world.
Participation in Pokemon Go once again saw parents interacting with their kids and driving them to different locations in the hope of catching digital monsters. People from all walks of life engaged with the game as a community.
Witnessing this ignited our imagination, and PokeCircle was born.
We’d love you, your family and friends to join us in making our social vision a reality.
SCRUM rules the world, the developer’s world.
Most software development teams we come across during job interviews work within an agile development methodology and, in the main, that methodology is SCRUM. That’s how it would appear at first glance in any case, but if you drill down you soon discover that the methodology used is not really SCRUM at all. If you consider what Scrum Alliance defines, for example, you’ll discover that some absolutely key elements of the SCRUM process are not employed, such as the right roles, the team concept, responsibilities, meetings etc.
So, how do you know if you’re really working in SCRUM? The SCRUM methodology is a framework and can, and should, be adapted to your particular project’s needs. Naturally, SCRUM may vary to some degree depending on the organization, the team, the project and the technologies employed. But, there are a few cornerstones of the framework that are unalterable, and those are related more to a way of thinking than to particular aspects of organization.
Consider the following simple questions:
- Is the work structured in increments of a regular size which are based on time rather than on scope? (sprint).
- Is each sprint planned with sufficient detail and is it clear to each team member what will be the result of the work?
- Does the team have full control over the ability to deliver planned tasks?
- Who is estimating the effort required to complete each task?
- Does the work in a sprint get interrupted by “very important” tasks? How does this affect the planned sprint?
As you’ve probably noticed, in this short list there’s nothing about meetings, daily scrums, planning or review as those are actually part of the SCRUM methodology. Some teams do get these few isolated aspects of the methodology right. However, the process can’t actually be called SCRUM as it’s sorely lacking the right mindset to employ SCRUM fully and effectively (the exception being retrospective perhaps).
However, what is often badly missing is the shift of responsibility from managers to the development team and, related to this, the central role of team commitment in the process. In my view, there cannot be a SCRUM without team responsibility, and to make it fair, without the team’s full control over the ability to deliver at the end of the sprint.
Obviously, there are many factors that can affect the team’s ability to deliver and thus the team’s commitment. Requirements might be unclear at the time of planning or could change during sprint. Dependencies on other parties might hinder starting work on a task. Sometimes it’s not even possible to estimate a task due to a lack of knowledge in a particular area.
Therefore, it requires the constant work of all involved parties, including the team, the SCRUM master and management, as well as the customer to create the right environment.
In today’s value driven medical environment the ability of the insideoutcomes software solution to provide accurate, actionable data through patient reported outcomes is more critical than ever before.”
Insideoutcomes delivers exceptional value to providers by putting affordable patient reported outcomes at the fingertips of medical professionals everywhere.
GET TO KNOW INSIDEOUTCOMES
We’re Delighted to be athenahealth’s Newest Marketplace Partner
Insideoutcomes provides online software services to medical professionals. Our software services enable users to track and report on patient reported outcomes (PRO’s).
Our cost-effective software solution uses a range of industry standard questionnaires that patients complete. At the moment we have in excess of 35 questionnaires in the system and this number is continually growing.
We use these questionnaires, in conjunction with our powerful reporting tools, to support evidence based medicine that precisely matches the needs of today’s value driven environment.
Insidoutcomes’ software as a service solution (SaaS) was specifically developed to address 3 key problem areas that medical professionals grapple with on a daily basis:
- Decreasing Reimbursement – meaning lower revenues for providers and less time and attention being available for patients as a result.
- Increasing Compliance Demands – resulting in more bureaucracy and the very real danger of non-compliance.
And the area we believe to be most significant of all:
- A Lack of Quality Measurement – creating an absence of accurate, actionable information which in turn negatively impacts effective doctor patient communication and reliable measurement of improvements in medical care.
Insideoutcomes is the only company to offer a fully integrated white-label solution for EHR software providers like athenahealth.
“Insideoutcomes proudly partners with athenahealth to provide objective metrics that empower providers to measure excellence, gauge the effectiveness of quality improvement programs and prove value to colleagues, partners and payers.”
The marketplace for clinical metrics software such as insideoutcomes is substantial and growing.
Currently, insideoutcomes is strategically focused on musculo-skeletal physicians such as orthopaedic surgeons and podiatrists. There are approximately 700,000 i doctors in the United States of which about 28,000 ii are orthopaedic surgeons and 15,000 iii podiatrists.
That said, there are questionnaires available in almost every medical field and we’re continually adding to and enhancing the insideoutcomes solution by building them in over time.
THE INSIDEOUTCOMES SOLUTION
The insideoutcomes software solution has a suite of powerful reporting tools that empower providers to prove value to payers, help insure compliance and accurately measure improvements in care.
In fact, the insideoutcomes solution goes even further than this. Our software also helps users identify opportunity for improvement, increase their referrals and wow their referring providers!
These, and other substantial benefits provided by the insideoutcomes solution, make our software a valuable weapon for providers in the war against being swamped by an ever-increasing workload and the imperative of avoiding compliance issues.
DELIVERING VALUE FOR PATIENTS
Using well documented and researched questionnaires, that are recognized worldwide, it’s possible to survey patients and measure indicators of improvement in a patient’s condition.
For example, medical professionals can determine a patient’s Minimum Clinically Important Difference (MCDI) which represents scores that reflect changes in a clinical intervention that are meaningful for the patient.
Based on well-defined metrics, we know how much a patient’s score should change from initial evaluation to discharge and therefore we’re able to judge the effectiveness (or otherwise) of a specific treatment.
DELIVERING VALUE FOR PROVIDERS
The demand for clinical metrics software has never been stronger than it is right now – the time is exactly right for the insideoutcomes solution.
In today’s value driven medical environment any tool that helps medical professionals improve quality of care and efficiency is in high demand, and insideoutcomes caters precisely for this demand.
The powerful reporting functionality built into the insideoutcomes solution is both flexible and, most importantly of all, actionable. This means that the data provided can be used to analyze quality, prove value and drive improvements.
THE ATHENAHEALTH & INSIDEOUTCOMES PARTNERSHIP
The athenahealth suite of services and insideoutcomes software solution have a natural affinity for each other and dovetail beautifully to provide a powerful, value-added solution in the EHR space.
Athenahealth is committed to “letting doctors be doctors” and this is a philosophy that insideoutcomes understands and agrees with wholeheartedly.
Working together, as marketplace partners, we believe athenahealth and insideoutcomes can provide an unbeatable EHR solution that has never been more in demand than it is right now.
In partnership, we can strive to “let doctors be doctors” by providing a powerful, seamlessly integrated solution that makes their lives easier and allows them to concentrate more on patient centric tasks.
As Aristotle famously put it “The whole is greater than the sum of its parts.”
CONTACT DETAILS HERE
i United States Department of Labor. Bureau of Labor Statistics. Occupational Outlook Handbook. Available at: http://bls.gov/ooh/healthcare/physicians-and-surgeons.htm Accessed January 25, 2016.
ii American Academy of Orthopaedic Surgeons. Orthopaedic Surgeons Quick Facts. 2014. Available at: http://aaos.org/CustomTemplates/Content.aspx?id=6408&ssopc=1 Accessed January 25, 2016.
iii American Podiatric Medical Association. FAQ About Today’s Podiatrists. Available at: http://apma.org/content.cfm?ItemNumber=8001 Accessed January 25, 2016.
NOTE FOR PORTFOLIO: insideoutcomes and athenahealth deliberately spelled with a lower case first letter in keeping with company branding.
The really cool thing about hybris is that the platform incorporates all major technology upgrades soon after they become available. This means you immediately have the chance to work with newest versions of languages and libraries such as Java, Spring etc. Recently, all our projects were upgraded to hybris version 5.6 and as a result we can now take advantage of Java 8.
Now, this opens up a whole host of new possibilities. Java 8 introduces a few fancy features that have been long awaited and well established in other languages. Features we believe you won’t want to live without once you’ve introduced them into your programming style.
A short list of these features can be found here:
Naturally, although this is the new standard, we still need to be cautious about how we use the additional features available in Java 8. They have to fit into our architectural guidelines and retain or improve the quality of our code’s maintainability and testability. After all, we know from past experience that some of these new standards have not made it into the mainstream, despite the support of Sun/Oracle; for example, java logging in JDK 1.4. Other features are of great value but can be radically misused if applied incorrectly.
So, we have started evaluating selected new elements of Java 8 in order to gather some hands-on experience with real commercial projects. The idea is to analyse the new features and have an internal discussion about how effective they are. We then want to come up with a set of guidelines as to what’s great, what’s cool or useful and what’s a no-go.
We’re very excited to be starting this exercise. To begin with, please take a look at the following Java 8 code:
.map(item -> item – item)
.map(item -> item * 3)
.map(item -> item.toString())
Yes, it is Java :). It’s not Ruby, Python or anything else. What this means is that we can now use a few key features of modern programming languages that were previously unavailable in Java.
- Lambda expressions and Functional interface (http://docs.oracle.com/javase/tutorial/java/javaOO/lambdaexpressions.html)
- Method references (http://docs.oracle.com/javase/tutorial/java/javaOO/methodreferences.html)
- Enhanced collection APIs (http://docs.oracle.com/javase/8/docs/technotes/guides/language/lambda_api_jdk8.html)
It all looks very promising and will certainly change the way we write code in the future. That said, there are certain caveats associated with these techniques, some of which we have discovered already and others that will become apparent in the future.
For instance, the above code is in conflict with our coding style which would not normally allow long chained statements. We have always had rules that make sense when it comes to code readability, and some static code analysis tools like PMD enforce those rules by raising alarms. This remains a positive and we will simply have to adapt these rules to the new concepts we are presented with.
However, for the optimal use of streams, these chained statements are essential. Methods should be passing (streaming) data to other methods while processing. Splitting the above into several lines would result in different behaviour in terms of memory usage.
This means, we’ll need to adjust the code style and reconfigure the tools – but we think it’s worth it.
So, we’re all now on Java 8, but we’re just beginning our hands-on research. We’ll be producing regular, information-packed updates on our progress and discussing the pros and cons of implementing the new features of Java 8 in real-world, commercial projects.
Stay tuned for more updates based on our experiences – coming your way shortly.