updated metadata template#34
Conversation
| @@ -1,3 +1,4 @@ | |||
| module InfernoTemplate | |||
| VERSION = '0.0.0'.freeze | |||
| LAST_UPDATED = 'YYYY-MM-DD'.freeze # TODO: update next release | |||
There was a problem hiding this comment.
This should be a real value. Note that this repo is really auto-generated from https://github.com/inferno-framework/inferno-core/blob/main/lib/inferno/apps/cli/templates/lib/%25library_name%25/metadata.rb.tt so we could update that to actually print out the current day.
Its fine for us to put a PR in this repo BTW as its easier to review, but to really 'persisit' it we'll need to put it in that template in inferno_core.
|
|
||
| E.g.: | ||
|
|
||
| > The ONC Certification (g)(10) Standardized API Test Kit is a testing tool for Health IT systems seeking to meet the requirements of the Standardized API for Patient and Population Services criterion § 170.315(g)(10) in the ONC Certification Program. It is an approved test method for the § 170.315(g)(10) test procedure. |
There was a problem hiding this comment.
I guess I would be a little more comfortable if we put in something like US Core in here vs. a certification test kit, just because publishing policy-looking documentation makes it look like official content vs. just an example. Or maybe just replacing it with a 'dummy' certification program / criteria. E.g. The Inferno Template Test Kit is a testing tool for Health IT systems seeking to meet the requirements of the API Criterion within the Example Certification Program.
| @@ -5,14 +5,89 @@ class Metadata < Inferno::TestKit | |||
| id :inferno_template | |||
| title 'Inferno Template' | |||
There was a problem hiding this comment.
I think we should make all fields feel as real as possible. E.g. Inferno Example Test Kit. or 'Inferno Template Test Kit'.
|
Oh sorry you only did one file to start, that's what you mean when you said 'this is only one file'. Disregard. |
|
These changes are now in #35 |
Summary
Additional guidance for documentation
Testing Guidance
None