Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have seen in FHIR CI site there is a new split of current Careplan and specially their components in several new Resources (Careplan2, CareActivity, Goal, ...)
Really, this is good because monolithic Careplan is very heavy for Careplan editors, and Careplan schedulers. We are finishing a Careplan Editor and a Careplan scheduler and really it´s heavy to keep all of this info related in a careplan or only one resource, specially for searching Careplan activities.
We will be very interested for modifying our CarePlan editors and scheduler because we could get better management.
My questions are:
- will these experimental Care plan proposals substitute the current Care plan? is there some scheduled proposal for this?
- Which group is defining this for collaborate with them?
Thanks in advance
Regards
Discussions around the scope of care plan are on-going. The alternatives you've found are definitely experimental, and I don't know what their standing is in terms of the editorial process. I do think that in the end, some kind of unpackaging is more likely than not doing it, whether it's this or not.
The work is being carried out by the patient care work group and HL7 (http://www.hl7.org/Special/committees/patientcare/index.cfm) and you should subscribe to the group email list.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 4 years ago.
Improve this question
I am new to software engineering and also I like to learn whatever new. I must be very thankful if someone help me to provide further information about How is a UI evaluated?.
Any help regarding to this matter is highly appreciated.
In common, evaluation of User Interface can be based on three common elements
• Functionality
• Aesthetics
• Performance
Functionality
Is the application usable?
Does it enable users to complete tasks?
Aesthetics
Style
How it influencing the users
How shown and presented?
How colors complement each other?
How UI elements convey their meaning?
Performance
Measured not only by speed, but also reliability.
Reliability (Even though an application looks good and feels great, crashes repeatedly, it likely won’t be very successful)
Should provide a user with full confidence.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I can't say I'm weak in programming but I can't come up with the logic faster. I can analyse others code and get to know the logic. But I can't do it on my own. How can I improve my programming skills?
Quite a broad question but from my own, 30yr experience I can tell you there is no way around starting to
analyze existing code,
modify some things (play with it until it feels like it's your own code)
see what the changes do
develop your own ideas on how to do things faster/better/more beautiful
implement your ideas
see if it works
go on to more complex tasks
read books (very important, because many things can't just be discovered by trial'n'error)
be very passionate and determined about what you want to become reality
if you want to learn faster, then write more code
One very important item. You should have fun with what you do is always the best guarantee for success
If you fail at these items then I'm afraid you will never succeed with programming. But then maybe it's like any other field of knowledge.
I experience the same difficulties during my learning journey, too. When I complete challenge tasks I create more complex tasks for myself to see what I can do. It takes me to the next levels of solving problems.
Practice, Practice, Practice!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I have 5 apps that I want to make right now, but creating them one by one seems inefficient. It seems like a better idea to make them all at approximately the same time in order to share segments of code where applicable. What are your thoughts on the most productive way to create a long list of moderately complex apps? For comparison, let's put them all on the difficulty level of a familiar & simple app - SnapChat.
Even though it sounds more efficient this sounds like a surefire way to either at best waste time or at worst (and most likely) get a lot of half written apps that never get to production. Unless this is a white label app where instead of 5 separate apps there is one app with 5 different skins you will likely never finish one of them let alone five. A 'simple app' like Snapchat still requires a lot of development time and testing, user adoption studies, and most of all focus of your effort.
Based on your question you have a good deal to learn about the development process. That is fine, you can do it, but focus on the best idea and put all your effort into that. It will take a lot more time and work than you expect and you will be happy you aren't worried about four other projects.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
Scrum is one methodology in agile software development right? What are the main activities in Scrum?
I hope this will help.
Nains...
Scrum is indeed an agile software development methodology.
It's more then a set of activities - there are a set of core assumptions and ideas that underlie the activities. Nains' answer contains a cheat sheet explaining very briefly the important concepts.
To answer your question in the most basic sense.
Gather user stories
Determine priority within these stories, chop them up in small, manageable tasks.
Code-code-code
Every day: short meeting where team members explain their progress, what they're working on, and where they get stuck on.
Every two weeks (or week, or month... depends on your project): deliver a working copy of what you have.
Return to step 1.
One such loop is called a Sprint. The essential step is that you begin by revisiting your assumptions what the software needs to do - the user stories, and their priorities.
Also note that this is a short cycle, within a very short period of time, the users get feedback.
Note that there is a lot more to be said about Scrum - if you want more details, I recommend a good book, or at the very least reading the Wikipedia article.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Someone within my organization has started pushing for us to pilot the CMU SEI's TSP process (see website here). I have an instinctual aversion to any attempts to cure software development illnesses with alphabet soup, but I would like to know if anyone has experience with this process and can provide tangible facts.
I used to be a fan of SEI's CMM. I even read Watts Humphrey's "Managing the Software Process" book cover to cover. I haven't used TSP but I suspect it has similar strenghts and weaknesses as the other software processes.
Definitely read about it and what they claim it can do and how to implement it, but be vigilant about keeping your software process small and flexible. You need one, but be careful about taking processes from someone else.
good luck.
We've been using this process for a few months now and I'm not particularly impressed. This process is only suitable for a strict command and control style of management where programmers are essentially bean counters. Most of the good parts of this process (size estimates rather than time estimates, self reviews, detailed plans, logging time against plans, and keeping a log of defects and errors for later review) can be implemented without throwing a bunch of money at SEI.