Create guide and process for web deployment of stand alone code

[mellybelly]

Command line tools such as LOINC2HPO need a place to live for kicking the tires. Cloud deployment of such tools could serve as guidance for the whole cloud architecture. @pnrobinson @kingmanzhang @eichmann

Related to data2health/cd2h-labs2#5

@prpayne5 assigning to you for your first thoughts. @jguinney how have you been handling this?

[pnrobinson]

We can provide a command line demo. Alternatively we can provide a SMART on FHIR app. Please contact us and tell us what we need to do for this!

[mellybelly]

This is a great project to help us start development of the software best practices. Recall from the FOA:

Promote software development standards for interoperability by:

• Creating and/or enhancing the use of software development standards. There is high need for the development and use of software development standards in order to facilitate the creation of collaborative informatics tools, methods, processes, and technologies that will be widely used to advance translational science.

• Facilitating the collaborative engagement of other stakeholders [e.g. federal partners and standards bodies such as the National Library of Medicine (NLM), Food and Drug Administration (FDA), Health Level Seven International (HL7), Office of the National Coordinator for Health Information Technology (ONC), Clinical Data Interchange Standards Consortium (CDISC), etc.].

• Supporting best practices to ensure the licensing of products, methods, and processes developed with the support of federal funds are freely available (open source) for the CTSA Program community and other stakeholders. This may include the following considerations as consistent with standard software development life cycle requirements:

  • Quality control: assurances that all products developed under this cooperative agreement meet the highest standards of quality including usability, functionality, dependability, interoperability, security, deployment and maintenance.

  • Accessibility: products that are developed under this cooperative agreement should become a national resource that could be used within the collaborative informatics laboratory environment and be accessible to all investigators.

  • Provenance: Ensure derivatives of the products are owned by the authors of said products. Maintenance: Plans for maintenance of the products produced.

  • Support: Ensure that customer support is available and responsive.

  • Interoperability: Ensure that all products developed under this cooperative agreement could be interoperable and that the source code will be accessible.

  • Evaluation measures: Metrics for performance of the product should be made available.

[mellybelly]

Also this just came out from GA4GH today, also relevant to best practices. https://github.com/ga4gh/data-security/blob/master/SecurityTechnologyInfrastructureV3.md

[davedorr9]

Melissa asked me to look at this. My only suggestions are as follows: 1) The aim sounds like github - a versioned code repository - github has tools to facilitate web deployment + an environment - one can containerize applications but automated web deployment of any code isn't obvious to me; 2) The grant is specifically asking for an evaluation against those criteria, and it seems like that is independent of any particular application. I think that's an interesting process. 3) For the specific application mentioned about, SMART on FHIR is a specific environment with tools already - or you could choose something like HSPC or another incubator site. I think they do not currently meet your requirements but could, perhaps, if the specific requirements are laid out to them.

[pnrobinson]

Could I suggest that we defined the intended audience and scope of this website? I am somewhat confused by the discussion so far, and it seems to me we should first clarify our goals before we decide on the "how".