[![Codacy Badge](https://api.codacy.com/project/badge/Grade/92419cae03cf4d769485c065b34efafb)](https://www.codacy.com/manual/FNLCR_2/icdc-codebase?utm_source=github.com&amp;utm_medium=referral&amp;utm_content=CBIIT/icdc-codebase&amp;utm_campaign=Badge_Grade) 

# ![ Image 1](doc/logo.png)

The [Integrated Canine Data Commons (ICDC) project](http://caninecommons.cancer.gov/) is a joint project between FNL's ADRD and BIDS Directorates to develop the ICDC for NCI's DCTD group.

The ICDC will create a new, dynamic data commons for canine cancer data, including not only clinical outcomes and genomics findings from canine clinical trials being conducted by the Comparative Oncology Program (COP) in collaboration with DCTD, but also the trials’ molecular, pharmacological, microenvironment, medical imaging and other study data.





## General Overview and Design Guidelines

![ Image 1](doc/system.png)

ICDC has two layers,Front-end and Back-end. Front-end is written in React.js and back-end follows API design is coded in JAVA. We put two layers together as a Java application. The figure above shows how system works and how back-end response the request. 

Client as an API consumer send a request, the JAVA servlet will capture the event and dispatch to the right endpoint. 

Client requests a web page, the JAVA servlet will capture the event and redirect the request to the React Component, React use Express to handle the request and render the HTML to the client.


Back-end provides two types of APIs , GraphQL and REST for purposes. 

## Folder Structure




 .
 ├── doc 	 		# Documentation files 
 ├── src 	 				
 │	├── main 			 	 		
 │	│	├── asciidoc			# API document template 
 │	│	├── frontend			# Front end source files
 │	│	├── java/gov/nih/nci/icdc 	# Back end source files
 │	│	├── resource			# configuration files
 │	│	└── webapp			# web html files
 │	└── test				# Test scripts
 ├── mvnw 
 ├── mvnw.cmd 
 ├── pom.xml 			 		# Maven POM file 
 └── README.md

## Set up

* dependencies 

Java SE Development Kit 11 


Tomcat 9


Maven 3.1


Neo4j Server ( Require to install neo4j graphql plugin )


* Configuration 

Change the neo4j.graphql.endpoint point to your Neo4j Server's graphql endpoint. In the application.properties change the setting:
	
	
	neo4j.graphql.endpoint =https://localhost:7473/graphql/


	 

* Maven Package project into War file. 

Use Maven to build the whole project into War file. Details can be found in POM file.

	mvn package

* Deploy war file to the tomcat



## Front End

After deploy to the tomcat, should able to see the page like this. 


 -<img src="doc/frontEnd.png" width="80%">
 

## GraphQL Endpoint

The Graphql endpoints have three components: domain, version and query.


	https://domain/<version>/graphql/ 

* Domain

Website URL

* Version

 API's version ( v1 as version 1) 

* Query

GrapQL query denotes the data wanted. 

Example query:
	
	# get studies by program id
	{
	 studiesByProgramId(program_id: "COP") {
	 program_id
 clinical_study_designation
 numberOfCases
 clinical_study_name
 }
 }




ICDC only support http POST method for GraphQL Endpoint. 

The picture below shows how to use POSTMAN to query the GraphQL. 

-<img src="doc/postman.png" width="80%">


## REST Endpoint

The Graphql endpoints have three components: domain, version and query.

The formate looks like below:

	https://domain/<version>/rest/<query>


Example query:

	https://domain/v1/rest/programs

Harness real-time device data and longitudinal health records to triage patient risk for diabetes

According to the CDC, over 100 million adults are living with diabetes or pre-diabetes in the United States. Given the complex approach required to help lower A1C levels and prevent or reduce diabetes complications, managing this group has posed healthcare professionals with immense challenges. KenSci’s solution provides out of box AI capabilities to risk stratify high risk population and predict time to:<o:p></o:p> 
<ol start="1" type="1"> 
 <li class="xmsonormal">Pre diabetes to diabetes progression<o:p></o:p></li> 
 <li class="xmsonormal">Uncontrolled Diabetes<o:p></o:p></li> 
 <li class="xmsonormal">Diabetes related complication like Chronic Kidney Diseases<o:p></o:p></li> 
 <li class="xmsonormal">Higher utilization and hospitalization</li> 
</ol> 
<ol start="1" type="1"> 
</ol> 
The KenSci AI driven Remote Diabetes Management solution, powered by Azure IoT Connector for FHIR helps care teams remotely manage their at-risk diabetes population using real-time device data&nbsp; from continuous glucose monitors, activity tracking devices combined with longitudinal health record information. &nbsp;KenSci’s machine learning driven risk stratification and recommendation system automates the complexity of prioritizing at risk patients and surfaces the right intervention to fill gaps in Diabetes care in real time.&nbsp; 
<div class="O1"> 
 <div>
 The out of box solution integrates seamlessly with existing care Management tools, patient engagement tools and acute care systems in hospitals and healthcare ecosystems and can be utilized by device manufacturers as they design new products. 
 
 </div> 
</div> 
The deployment of this solution involves 5 key stages: 
<div class="O1"> 
 <ol> 
 <li>Reference Architecture - Standardized infrastructure for enterprise Data and Cloud workloads with FHIR service</li> 
 <li>Data on-boarded on Azure - Seamless data onboarding and ingestion pipeline to bring in data at scale from devices to FHIR service&nbsp;</li> 
 <li>Data transformation - Map device data with patients and prepare for analytics and Machine Learning</li> 
 <li>Analytics Dashboard - Embedded analytics in KenSci's analytics portal, uncovering key insights to aid in patient monitoring</li> 
 <li>ML-based insights - Extend to include predictive risk stratification models for patient population leveraging data collected by devices, EMR, Claims, labs etc.</li> 
 </ol> 
</div>

Rapid implementation, validation, and maintenance to achieve GxP compliance of your Azure tech-stack

<h3>USDM enables pharmaceutical, biotechnology, and medical device companies to transform their GxP workflows with Unify Public Cloud&nbsp;for Azure. The solution addresses SaaS (business applications), PaaS (cloud services), and IaaS (global infrastructure). All packaged in USDM’s Cloud Assurance&nbsp;subscription to manage ongoing updates and decrease your compliance burdens.<o:p></o:p></h3> 
 <o:p>
 &nbsp; 
 </o:p> 
FEATURES<o:p></o:p> 
Unify Public Cloud&nbsp;provides expert compliance services, fast-start accelerators, and defensible validation deliverables based on 20+ years of life sciences solution delivery.&nbsp;&nbsp;<o:p></o:p> 
<ul type="disc"> 
 <li class="MsoNormal">Expert Compliance Services&nbsp;– an Annual Vendor Audit, Infrastructure Qualification, Cloud Services Qualification, Cloud Application Validation, and an IS Health Check&nbsp;<o:p></o:p></li> 
</ul> 
<ul type="disc"> 
 <li class="MsoNormal">Fast-Start Accelerators&nbsp;–&nbsp;Impact Assessments, Procedures &amp; Controls, Change Management, and Qualification Package<o:p></o:p></li> 
</ul> 
<ul type="disc"> 
 <li class="MsoNormal">Defensible Validation Deliverables&nbsp;–&nbsp;Qualification(s), Qualification Plan (System Requirements, Configuration Specification, CQ/PQ, Qualification Report), USDM’s Assurance Report and Vendor Certification<o:p></o:p></li> 
</ul> 
 <o:p>
 &nbsp; 
 </o:p> 
BENEFITS<o:p></o:p> 
By leveraging USDM’s life sciences expertise and accelerated cloud services, you can rapidly implement a GxP compliant framework.<o:p></o:p> 
<ul type="disc"> 
 <li class="MsoNormal">Reduce your compliance risk&nbsp;and&nbsp;achieve continuous cloud compliance&nbsp;with USDM’s framework and accelerators for Azure<o:p></o:p></li> 
</ul> 
<ul type="disc"> 
 <li class="MsoNormal">Speed deployment and adoption of Azure&nbsp;and Microsoft business applications with&nbsp;prepackaged solutions built-on life sciences best practices<o:p></o:p></li> 
 <li class="MsoNormal">Accelerate your cloud journey&nbsp;by&nbsp;identifying strategic business initiatives&nbsp;made possible with Azure<o:p></o:p></li> 
</ul> 
<ul type="disc"> 
 <li class="MsoNormal">Flexible cloud adoption model&nbsp;to migrate regulated workloads<o:p></o:p></li> 
</ul> 
<ul type="disc"> 
 <li class="MsoNormal">Cost-effective, bundled solution&nbsp;to minimize barriers to compliance and innovation<o:p></o:p></li> 
</ul> 
<ul type="disc"> 
 <li class="MsoNormal">Build value-creating activities, decrease value-consuming activities<o:p></o:p></li> 
</ul>

Healthcare Libraries - Page 22

icdc-codebaseby CBIIT

JavaScript 0 Version:Current
License: No License (No License)

Old ICDC repository, please don't use!

Remote Diabetes Management with Azure IOT for FHIRby KenSci

cloud_api 0 Version:Current
License: Proprietary (Proprietary)

Harness real-time device data and longitudinal health records to triage patient risk for diabetes

USDM Unify Public Cloudby USDM

cloud_api 0 Version:Current
License: Proprietary (Proprietary)

Rapid implementation, validation, and maintenance to achieve GxP compliance of your Azure tech-stack

icdc-codebaseby CBIIT

Remote Diabetes Management with Azure IOT for FHIRby KenSci

USDM Unify Public Cloudby USDM

Open Weaver – Develop Applications Faster with Open Source

kandi

Community and Support

Company

Follow

Healthcare Libraries - Page 22

icdc-codebaseby CBIIT

JavaScript 0 Version:Current License: No License (No License)

Old ICDC repository, please don't use!

Remote Diabetes Management with Azure IOT for FHIRby KenSci

cloud_api 0 Version:Current License: Proprietary (Proprietary)

Harness real-time device data and longitudinal health records to triage patient risk for diabetes

USDM Unify Public Cloudby USDM

cloud_api 0 Version:Current License: Proprietary (Proprietary)

Rapid implementation, validation, and maintenance to achieve GxP compliance of your Azure tech-stack

icdc-codebaseby CBIIT

Remote Diabetes Management with Azure IOT for FHIRby KenSci

USDM Unify Public Cloudby USDM

Open Weaver – Develop Applications Faster with Open Source

kandi

Community and Support

Company

Follow

JavaScript 0 Version:Current
License: No License (No License)

cloud_api 0 Version:Current
License: Proprietary (Proprietary)

cloud_api 0 Version:Current
License: Proprietary (Proprietary)