Personalized Medicine – Concept or Reality?

Personalized Medicine – Concept or Reality?

 

 

 

 

 

 

 

 

TAKE NOTE (Insights into SAP solutions and Emerging Technology)

Technology is the Driving Force

By leveraging high speed in-memory analytics technology, healthcare organizations can now comprehend astronomical amounts of data. And by tapping into all this data, like patient EMR information, healthcare professionals can categorize patients into micro-buckets based on ethnic, environmental, lifestyle, and DNA similarities. From there, they can make educated predictions on how different patients will react to different treatments.

With faster access to more effective treatments, physicians have time to serve more patients without sacrificing quality of care.

The American Society of Clinical Oncology (ASCO) Proves the Effectiveness of Data Sharing

Through its pioneering initiative, CancerLinQ™, ASCO has created a real-world, rapid learning healthcare system that aims to help oncology professionals analyze and share data on every patient with cancer.

“The number of participating practices and providers continues to grow all across the United States, already contributing to over one million patient records in the CancerLinQ™ system,” said Jennifer L. Wong, Chief of Strategic Alliances for CancerLinQ LLC.

CancerLinQ™ leverages SAP HANA to harness, assemble, and analyze all of the information flowing into the system.

“The more data we have on patients, the better chance we have of providing faster, more relevant, and actionable information to drive informed decision-making, potentially enabling more targeted treatments for more people. Currently, only 3% of cancer patients are enrolled in clinical trials. With CancerLinQ™, we can someday tap into information on the additional 97% of cancer patients in the real-world setting, significantly impacting treatment decisions to improve care,” said Wong.

Read more here at Forbes. 


UNDER DEVELOPMENT(Information for ABAP Developers)

Predictive Search Helps in ABAP 7.4

So you want to find a book on ABAP, so you head over to your favorite browser and using Google start typing in ABAP and instantly you see search results. (see below)

 

 

 

 

 

 

 

 

 

 

What if this “type ahead” (Predictive) or “search engine like” functionality could be used in our ABAP 7.4 Search helps?

Well, the good news is it can. You need to be on SAP NetWeaver 7.4 SP06, and SAP GUI 7.30 for Windows Patch Level 5, SAP recommends Patch Level 6 or higher. You can use this on  ABAP 7.4 SP05, but you will need to add a PBO section in your DYNPRO to call class CL_DSH_DYNPRO_PROPERTIES=>enable_type_ahead.

At the end of this blog, I will add a link to a SAP video that explains this and much more in detail. For this blog, I am on the correct support pack and GUI, so this will all be done with any coding changes.

First, let’s look at the code that invokes the Search help.

Read More.


Q&A (Post your questions to Facebook or Twitter and get the answers you need)

Q. In productive system of my Webdynpro Application I get a 500 Internal Server Error when calling an RFC Function. In test system everything works fine. Can you give me a hint, what the problem could be? I have no idea where to start the search!

A. When you call an RFC-enabled function module, an error may occur. Depending on the error handling of the application, the following situations may arise:

1. The application does not catch the RFC exceptions (in the error situation, the ABAP runtime error CALL_FUNCTION_REMOTE_ERROR occurs; for more information, see Note 97522).

2. The application catches the RFC exceptions but does not provide the caller with the RFC message text that was received; instead, it provides a fixed message text that does not help with analyzing the error.

As you mentioned it works in the TEST environment, so more than likely the RFC is being called by a user that is either locked or even not defined in Production. Here are a couple of steps you can take.

– Check the dumps on each side in Thier respective systems using ST22

-In the program issuing the calling RFC, add the following two additional exception types:

SYSTEM_FAILURE

This exception reports all failures and system problems on the remote machine.

COMMUNICATION_FAILURE

This exception is raised when a connection or communications failure occurs. It does not report system problems (for example, abnormal termination) that occur on the remote machine.

The code looks like this…

CALL FUNCTION Remotefunction

DESTINATION Dest

EXPORTING…

IMPORTING…

TABLES…

   EXCEPTIONS

     SYSTEM_FAILURE = 1 MESSAGE msg

     COMMUNICATION_FAILURE = 2   MESSAGE msg

The system sets the message variable (msg) to the system message. You can then display the message or log it in a file. You should not try to interpret message text in your program.

Hope this helps!

 

 

 

 

Pin It on Pinterest

Share This

If you enjoyed this post, why not share it with your friends!