Search Mailing List Archives
[bioontology-support] [External] Re: Bioontology APIs
RAMACHANDRANM at email.chop.edu
Mon Apr 8 07:28:04 PDT 2019
My apologies for the delay in getting back to you.
Since we are a pediatric hospital, we have to go through certain process before something like a testimonial can be added to an external web site. We are working with the necessary teams at CHOP to understand the process. We will let you know as soon as we have the necessary information.
Regarding the SSL issue (ref: below), it looks like the cert is still in the expired state. Will it be possible for your team to renew the cert and address the issue? We would like to communicate with your site through a secure channel.
[cid:image001.png at 01D4EDF5.BE479640]
From: John Graybeal <jgraybeal at stanford.edu>
Date: Thursday, March 7, 2019 at 5:20 PM
To: "Ramachandran, Manoj" <RAMACHANDRANM at email.chop.edu>
Cc: "support at bioontology.org" <support at bioontology.org>, "info at bioontology.org" <info at bioontology.org>, Len Minkovsky <MinkovskyL at email.chop.edu>, Anbumalar Singaravelu <SINGARAVELUA at email.chop.edu>
Subject: [External] Re: [bioontology-support] Bioontology APIs
Thanks for your testimonial! (May we use it in our web site?)
I'll let the technical team address your questions, but I want to explore your second question about reliable access. (We have a similar question for our CEDAR  project: how can we maximize reliability of its queries to BioPortal? Obviously local caches could be used, but of course you'd have to update them regularly.) The difficulty is what you mean by "the data"—there are very many ways to request, subset, and organize data requested via the API—more ways than you could possibly cache. Assuming you had a very specific set of information you wanted to store, the fastest way to get a dump of that data might be to construct the queries to just find those attributes. Since not all of our information lives in a single database, we would need to understand precisely which information you are looking for, in any case.
In the end, a faster way to obtain reliable access to the data could be to run your own BioPortal instance (but that takes some effort). We also can offer dedicated services to meet Service Level Agreements; please contact me off-line if you wish to explore that further.
 Center for Expanded Data Annotation and Retrieval: https://metadatacenter.org
On Mar 6, 2019, at 9:37 AM, Ramachandran, Manoj <RAMACHANDRANM at email.chop.edu<mailto:RAMACHANDRANM at email.chop.edu>> wrote:
Your site provides valuable information for our departments and we are planning to use the APIs provided through the site for our internal workflows for our EHR system. Thanks for providing us with such valuable information.
We have some workflows developed in our development environment and recently noticed that there were issues communicating with the APIs because of cert issues (ref: screenshot below). Can you please update the certs on your side so that we can communicate with your servers/services on a secure way.
Also we are trying to see if there is a way we can get a dump of the data in json format so that we can store in locally and use it as a backup resource in case we cannot reach the site. That way our workflows can still stay intact. Please let us know your thoughts on this.
IS Developer Principal, Application Development
3401 Civic Center Blvd.
Philadelphia, PA 19104
o 267-426-1757 ● m 610-745-3566
ramachandranm at email.chop.edu<mailto:ramachandranm at email.chop.edu> ● chop.edu<http://chop.edu/>
bioontology-support mailing list
bioontology-support at lists.stanford.edu<mailto:bioontology-support at lists.stanford.edu>
**** This email originated from an EXTERNAL sender to CHOP. Proceed with caution when replying, opening attachments, or clicking links. Do not disclose your CHOP credentials, employee information, or protected health information to a potential hacker****.
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 342172 bytes
More information about the bioontology-support