DEV Community: nubentos

CARDIO API, by Nubentos

nubentos — Wed, 24 Jun 2020 05:24:56 +0000

Hi!

Just another short post to share with you exciting news!

Our brand new API, Cardio API, is available now in Nubentos API Store! (applause)

Yes, after the success of our COVID-19 tracking API, ranking #1 in Apimetrics listing, we have been working in new ideas that will be developed in the forthcoming months.

Cardio API is our grain of sand to help fight heart diseases worldwide.

In particular, Cardio API returns an estimate of the atherosclerosis cardiovascular disease (ASCVD) risk according to the 2013 ACC/AHA Guideline on the Assessment of Cardiovascular Risk and the 2013 ACC/AHA Guideline on the Treatment of Blood Cholesterol to Reduce Atherosclerotic Cardiovascular Risk in Adults.

Different algorithms calculate this risk for different ethnic groups, since there are evidences that estimations vary from certain racial groups to others. We will add them in future versions to cover as many cases as possible. This first version uses the algorithm that shows accepted estimate for African-American and non-Hispanic white men and women 40 through 79 years of age.

There are a number of Apps and websites that offer this feature to their users. Why yours should offer less?

Have a closer look to its microsite here, and please share with us your thoughts about any aspect of our brand new API.

We are paying special attention to pricing, because we want to make this profitable and affordable for you.

We've started from these pricing plans, but are opened to your suggestions and thoughts, so do not hesitate and let us know the cons you find (if any):

Freemium tier: in this tier you can play with the API up to 100 requests per month at no cost. Overuse will charge 0,05€ per request.
Basic tier: here you have up to 1.000 requests per month with a small fee of 0,005€ per request. For example, with 300 requests you will be charged 1,5€. Remember that in Nubentos costs are auto scaled: it goes along with the real use made by your users. Again, extra requests have a 0,05€ per request fee.
Pro tier: allows you up to 10.000 requests per month, for 0,0075€ per request. This is, for example, 22,5€ for 3.000 requests.
Payperuse tier gives you unlimited requests per month, with a constant fee of 0,01€ per request.

Again, we encourage you to share with us your suggestions. We are looking forward to learning and to helping, and nothing better than your point of view to do so.

We want to help Digital Health reach as many people as possible worldwide, and that will be possible only with YOUR help. So please, help us do things better and better!

Thank you and happy integration!

6 great benefits of using Nubentos for your Health Apps

nubentos — Thu, 04 Jun 2020 08:53:02 +0000

If you develop Apps, surely APIs don’t hide secrets from you. If you also develop Apps for Health and Wellness, then maybe you know Nubentos, the API Marketplace for Health. Whether you already know us or not, now you will discover our selection with the 6 great benefits of using Nubentos for your Health Apps.

Are you ready? Here we go.

1. Access a growing catalogue of APIs for your Health Apps

Hundreds of companies around the world offer advanced Digital Health services through APIs or through eligible services. Do you know them?

It is really difficult to know the innovations in Digital Health that exist in the world, available to integrate in your Health Apps. You need a place that brings together these innovations and makes them available to you so that you can learn about them and improve your Apps or create new ones that will stand out among the hundreds of thousands of Apps available.

That place exists and is called Nubentos.

2. Test the APIs as long as you want, without cost and without code

Besides discovering the APIs that you can integrate into your Health Apps, what would you like to do?

We think it would be great to be able to test it, and if possible, at no cost and without the need to code anything.

That’s why there is an API Console in Nubentos, an online test console, which allows you to test every API resource in a sandbox environment, as long as you want, and without any cost.

This way you can, on the one hand, confirm that this API does what you need for your Health Apps. On the other hand, it allows you to perfectly understand how it works, how its input parameters are informed, and what response it returns.

Thanks to this, your development and testing time is drastically reduced, and with them, your time to market is optimized.

3. Use any of the 10 SDKs available for each API in your Health Apps

Well, you’ve already discovered APIs for Health that you didn’t know about, and you know that you’ll find new APIs in Nubentos as our catalog gets populated.

You have also tried that API you are interested in, saving costs and development time for your Health Apps.

Now it’s time to integrate the API into your source code, so that your App offers your users that functionality.

As you know you can use the endpoint directly and work directly with the resources. But if you do not want to complicate yourself or if you or your team do not have enough experience, in Nubentos you have 10 SDKs for each API, to make coding much easier.

Obtaining and renewing the token, calling each resource, managing the response and possible errors… everything is covered in the SDKs.

An SDK for each of the main web and app development technologies on the market. It would be very rare that you don’t find the SDK for your project.

4. Manage the tokens for your Health Apps on the same platform

You integrate the API of provider A into your App, and manage your permissions and authorization with that provider’s backend. You integrate Vendor B’s API, and now manage its token and permissions with that new Vendor B’s backend. So for each App.

What a mess, isn’t it? When one of these providers changes its backend, or the way it resolves the access to its API, you must adapt your affected Health Apps.

But in Nubentos you manage your tokens in a centralized way, since your Apps interact with the Nubentos Gateway.

As a result, even if your API providers make changes to your backend, your token management is not affected.

5. Delay auto-scaled costs for your Health Apps

Usually getting access to an API to integrate it into your Health Apps has an associated cost from the minute zero. Either you must pay a renewable license, or you must subscribe with a monthly fee that gives you the right to use the API.

In both cases, you assume costs even before you have tested the API, and throughout your development and testing cycle.

These costs remain regardless of whether your development is delayed or whether your users will use the new functionality.

In Nubentos you access the API at no cost, you test the API at no cost, you develop the integration with your App at no cost, and the time it takes your App store to put it on sale, you still do not assume any cost. Even if your App takes a while to start getting downloaded and used, you save the cost.

The cost only appears when your end users start using the functionality you’ve integrated with the API in your App. And those costs are automatically escalated. If users stop using it, your costs disappear.

6. Monitor and control the traffic generated by your Health Apps users

Finally your App is being used by your users, and with it they start to make use of the new functionality provided by the API you have integrated with Nubentos.

How do you know what use they are making of it? How do you measure the return on investment of integrating an API with a cost? How do you control if usage is above or below your forecasts?

In Nubentos you have a set of analytics that allow you to monitor the use made by your users. This way you can know if you have chosen the right consumption plan for the real consumption you have in your Health Apps, and if necessary, you can adjust it by changing the consumption plan. This way you can optimize your costs and adapt them to your demand.

You also have the possibility of establishing a throttling policy, to ensure that your traffic is properly distributed over time to avoid call bursts that could affect the performance of your APIs.

Using the Nubentos API Store to create new Health Apps and improve the Apps you already have on the market has many other advantages. Here we have selected the 6 most important advantages.

Would you highlight any other advantages? Tell us which one is your favorite by leaving a comment.

Thanks for reading and happy integration!

This post is also available at Nubentos' blog.

#1 in Apimetrics COVID-19 tracking APIs ranking

nubentos — Thu, 14 May 2020 00:12:30 +0000

Hi there!

Just a super short post to celebrate with all of you that Nubentos' COVID-19 tracking API is listed at the top of the Apimetrics ranking!

That deserves a "Wow!!", doesn't it. 🙌

You can access the ranking here.

Remember that version 2.0.0 is now available in Nubentos API Store, with new information and filters.

Almost 1,5M of requests in two months, and growing fast! Come on and use our APIs to build your amazing Apps!

Take care and happy integration!

AI for Diabetes, at your reach

nubentos — Sun, 10 May 2020 00:48:32 +0000

More than 400 millions of people colive with Diabetes everyday. Most of them use Apps quite often, and with no doubt, the most important App for them is the one that helps them manage their disease.

What can the diabetic patient do with current Apps?

Surprisingly, most of these Apps do little more than register the glucose values and draw some graphs. Just a few provide advice about diet and exercise routines. And even these ones usually give standard pieces of information, with no or little customization for each user.

Well, this can clearly be improved.

What about predicting glucose ups and downs? Diabetic patients know that everything they do about their disease is aimed at avoiding these dangerous values.

How many Apps for diabetes are able to predict the glucose levels for each user in advance?

Preventive healthcare for Diabetes

This feature has extraordinary applications in many research activities around Diabetes, buy let's focus here on the patients.

Adding the prediction of future glucose levels to your App functionalities, will multiply its value and would be an extraordinary aid to improve the user's quality of life.

The good news are that in Nubentos API Store, you can find the MedicsenAPI: a superfast API that allows you to remotely use their machine learning-based algorythm to predict the future glucose curve specific for each user.

Medicsen is a spanish startup focus on chronic diseases. They have recently been awarded with the first prize in the Virtual South Summit for Health & Wellbeing (yes, these guys know what they do).

Though their core business is the new generation of non-invasive medical device for diabetic patients, they have found the opportunity to share their core technology with the community of software developers through Nubentos API Marketplace.

MedicsenAPI, a closer look

In particular, MedicsenAPI receives a json file in the request, such as the following sample:

{
"Inputs": {
"predictor_input": {
"ColumnNames": [
"time",
"glucose",
"cho_simple",
"cho_complex",
"ins_fast",
"ins_slow",
"mass"
],
"Values": [
["2019/08/05 16:00", 120, 10, 40, 3.5, 0, 75],
["2019/08/05 16:15", 121, 0, 0, 0, 0, 75],
["2019/08/05 17:35", 132, 0, 0, 0, 0, 75],
["2019/08/05 18:45", 0, 0, 0, 0, 20, 75],
["2019/08/05 19:00", 140, 0, 0, 0, 0, 0]
]
}
},
"GlobalParameters": {}
}

Each row contains the glucose lecture, the ingested carbohydrates (simple and complex) and the injected insulin dose (fast and slow acting insulin).

When sending this request, MedicsenAPI returns the following response:

{
"Results": {
"predictor_output": {
"type": "DataTable",
"value": {
"ColumnNames": [
"pred0",
"pred15",
"pred30",
"pred45",
"pred60",
"pred75",
"pred90",
"pred105",
"pred120",
"pred135",
"pred150",
"pred165",
"pred180",
"time"
],
"ColumnTypes": [
"Numeric",
"Numeric",
"Numeric",
"Numeric",
"Numeric",
"Numeric",
"Numeric",
"Numeric",
"Numeric",
"Numeric",
"Numeric",
"Numeric",
"Numeric",
"Object"
],
"Values": [ [
”104.009263669471”,
”96.2364046604062",
"99.2647391878364",
"102.744641274917",
"106.089699255478",
"108.584562644434",
"110.679614334562",
"112.167824226935",
"113.470337538897",
"114.435026850847",
"115.118934184411",
"115.570538408333",
"115.831295991142",
"8/5/2019 7:00:00 PM" ]
]
}
}
}
}

Which contains the predicted glucose levels for the next 180 minutes, in 15 minutes intervals. Medicsen guys inform that the most accurate results are within the first hour ("pred60"), and beyond that, values should be treated with caution.

You can access the MedicsenAPI here.

You will find all their subscriptions plans, the API documentation, our online test console to easily learn how it works before coding, and our ten SDKs available.

To be able to run a test, please remember that:

You have to create an application and generate the keys for production
MedicsenAPI has no sandbox endpoint since their algorythm returns the same values for the same input, thus a sandbox endpoint would return the same response as the production endpoint.
Since they don't need to store any information, it makes no sense to publish a sandbox environment.

And that's all for now. We have more good news like these ones, and we will tell you about them quite soon. So don't miss our posts!

Thank you for reading and take care!

COVID-19 API - New version available

nubentos — Fri, 08 May 2020 23:33:28 +0000

Hi there!

Just a short text to let you all know that in Nubentos we have just launched the new version of our successful COVID-19 tracking API (nCov-2019 API), which is over 1M requests in just a couple of months.

Version 2.0.0 comes with new resources and indicators, and allows you to filter by country or continent.

In a nutshell this is what you will find in the new nCov-2019 API v2.0.0 by Nubentos:

GET /cases - Total of active cases.
GET /todayCases - Today cases.
GET /active - Active cases
GET /deaths - Total of persons death.
GET /todayDeaths - Today deaths.
GET /recovered - Recovered cases
GET /critical - Critical cases
GET /casesPerOneMillion - Cases per Million
GET /deathsPerOneMillion - Deaths per Million
GET /totalTests - Test Totals
GET /testsPerOneMillion - Test Per Million

As you can see, there's a lot of things that you can do now, that were not possible with the previous version.

Get ready for this new stage of the pandemic, where new outbreaks will need a close watch to keep them under control, and people will be willing to be informed.

In case you haven't signed up in Nubentos yet, do it now and stay tuned as we will keep our users properly informed for the deprecation of v1.0.0.

Access the API here, where you will find anything you need to test the API and easily integrate it in your digital products.

Spread the word!

Happy integration!

QuaranTIME API call for Apps!

nubentos — Wed, 06 May 2020 11:06:47 +0000

COVID-19. There's not much more to say, you know what we're talking about.

We are all, to a greater or lesser extent, affected by the pandemic. But as software developers, we can do a lot for the future in the short, mid and long term.

If you want to be part of something big, which like everything big is born from the humility of an utopian idea, read on.

The world facing a challenge

While some countries are facing the most acute phase of contagion, others are beginning the phase of deconfinement. A gradual return to normal, or something similar, by phases, which is a real uncertainty.

Everyone assumes that there will be outbreaks of the epidemic. The challenge now is to control these outbreaks so that they do not surprise health systems and society in general again.

How is the world preparing for this new phase of COVID-19? And in the process, for future pandemics.

Many governments, national and local, are planning a similar strategy based on deploying a process of tracking and monitoring positive cases. In summary, the process is described as a humane process that consists of interviewing the newly infected person by telephone to find out where he or she has been and with whom he or she may have coincided, looking for those contacts, classifying them as being at low or high risk, calling those people so that, if necessary, they can be tested, and including all the information in a computer application.

It seems that New York is planning to train between 6,000 and 17,000 people, the United Kingdom is talking about 18,000 and Germany will deploy 105 mobile teams financed by its Ministry of Health to reinforce this tracing work.

Some drawbacks of the plan

Let us think for a moment about three important factors in controlling outbreaks and resurgences of a pandemic:

Time. In an epidemiological process, time is key. With a virus that is incubating for 14 days, "tracking hours" can mean dozens or even hundreds of infections. The table above shows this clearly, assuming that each person infects only two other people, which is a very conservative assumption. Time moves down the tree of contagion. The sooner we detect the chain and interrupt it, the more people will be safe.
Cost. Whatever solutions are adopted, they will have a cost. But a system based on hiring and training a team of thousands of people who must work in perfect coordination, seems to me to be extremely costly.
Accuracy. Even if we find a cost and time efficient system, if we work with a high percentage of errors we are going wrong. And this approach is basing 100% of its success on the absence of errors or forgetfulness in the people involved (trackers and tracked).

A technology plan to truly control outbreaks.

What if that "army of trackers" were not human, but technological? What if that Database were informed by the same citizens who have massively complied with the confinement, demonstrating an unquestionable sense of responsibility? What if we focused on the automatic and intelligent exploitation of that Database for the automatic detection, in seconds, of the entire chain of possible contagions from a positive case?

Based on this new approach, let us now review those factors:

Time. The time factor is clearly reinforced. From an approach that takes many hours of investigation, to an automatic process that obtains the result in seconds.
Costs. Every technology has a cost, but I bet it is much less than maintaining a team of thousands of people hired, trained and coordinated.
Accuracy. This system will not depend on the memories of the infected person, nor on the excellence of the tracker's performance, nor on innumerable nuances inherent to our humanity that can affect the quality of the information. In this approach, it is the data, nothing more and nothing less than the data, that govern the identification of the possible chain of contagion.

This system is called QuaranTIME Integrated Solution (QIS) and was presented by Nubentos to the European Commission on March 20th and to the Instituto de Salud Carlos III a few days later. In 2 months it is possible to have a first operational version of the solution, with the necessary resources.

QIS - A collaborative project for a global reach

Our proposal has some differences from the rest of the initiatives of technological "tracking" of the population in a pandemic. But there is one that we consider absolutely key: collaboration.

If we bet everything on one App, we depend on that App to reach enough people. And each app will have its own limited database, so it will only serve the group of citizens who have it installed and in use. The moment a positive case would occur, the chain of potential infections that would be obtained would be incomplete in the vast majority of cases.

This is like wanting to control a whole forest by being a tree. We want to be the soil where that forest grows.

We want to offer the technological solution that allows the creation of a real "army" of technological trackers: Apps, many of them, the more the better. All working for QIS. All feeding the Big Data that allows to extract in seconds chains of possible infections from a positive, and with global reach.

A technological tool that wants to be effective in controlling a pandemic must have global reach. Otherwise we would be proposing an unequal fight, in favour of the virus.

That is why QIS relies on the QuaranTIME API, and why Nubentos proposes QIS as a necessarily collaborative solution.

The key role of App developers

From here we invite the community of software developers, app developers, to join the project to deploy as many apps as possible that use the Nubentos QuaranTIME API. We want to have Apps in the Americas, Europe, Asia, Africa, Oceania, connected to the Nubentos QuaranTIME API, providing data to data, the pieces of information that will allow to control the pandemic and help save many lives.

What does QIS track? Geolocation and especially proximity contact data. The former will allow us to know where the infected user has been, and the latter will tell us who he has been in contact with.

Nubentos QuaranTIME API, available for pre-registration

The Nubentos QuaranTIME API is available for pre-registration in our API Store. Whether you are a company or a freelancer, if you develop Apps and move or are interested in the Health and Wellness sector, do not hesitate and join us in a project as ambitious as it is transformative.

Together let's create the solution to the problem, for this and for future pandemics.

Access the Nubentos QuaranTIME API here.

Please help us spread the word about this project. Share it on your network, it will surely reach more teams interested in joining the project.

We will stop this virus together.