KIDS/Certification Submission Requirements

KIDS/Certification Submission Requirements

In order for a submission of code to be compiled into a KIDs file, and submitted for certification through the OSEHRA process, a number of artifacts and data points are required.  This wiki is to capture these elements, please use this document to identify them.

This document will overlap with the requirements of the certification process, and the working group associated with it.  We will work collaboratively to ensure the expectations of both of these efforts meet.

KIDS file Pre-requisite Element Summary:

Patch Number - Will be required.  Should be coordinated with VA patch stream.

Version Number - Will be required.  Should be coordinated with VA patch stream.

Test Number - Will be required.  Should be coordinated with VA patch stream.

Sequence Number - Not required for KIDs file build, more deployment side on VA stream.

NameSpace - Will be required.  Should be coordinated with VA .

NumberSpace - Should define reserved area for OSEHRA; though WV has volunteered theirs for the intial pass.

GIT Meta Information - TBD, used to inline documentation within KIDS?

Certification Pre-requisite Element Summary:

Release Notes

 

like0

Comments

KIDS/Certification Submission Requirements

conor dowling's picture
Matt, I don't know if this fits in but for anyone who doesn't know KIDS much and wants to browse what's in one, here are two as they show up in a live VistA (via FMQL). 1) a big, contain everything KIDS: ORDER ENTRY/RESULTS REPORTING 3.0, which added a lot of RPCs, Options, Routines, Files for CPRS access - this represented a big VistA milestone (as you can see from the size of the scroll bar in your browser after it loads) 2) a smaller one - only its "build components" - this is more like the routine-only one you want: DG*5.3*672. Beyond descriptions/other required builds, files, "build components" lists the different sorts of things that go in a build. This one only has options and routines but the titles of the other 17 possibilities show too (HL7, RPCs ...). If GIT is to support full VistA "software artifact" (is that the term David used?) management then it needs to capture build-component nuance in some way. Finally here's the schema of file 9.6 - what's in a KIDS. As George pointed out, VistA can build one of these "manifests" for you but if you want GIT->KIDS (via python ...) then you'd need to set GIT up to capture the nuance in KIDS (routines and globals doesn't cut it). After that a publish script shouldn't be difficult. Conor On Thu, Apr 19, 2012 at 9:31 AM, mmccall wrote: > In order for a submission of code to be compiled into a KIDs file, and > submitted for certification through the OSEHRA process, a number of > artifacts and data points are required. This wiki is to capture these > elements, please use this document to identify them. > ...
like0