Difference between revisions of "GPP guidance review"

From PHUSE Wiki
Jump to: navigation, search
Line 13: Line 13:
 
   
 
   
 
# Create an account on the PhUSE wiki (if you have not already done so.) . This is entirely free there is no requirement to have paid membership of PhUSE to do this.
 
# Create an account on the PhUSE wiki (if you have not already done so.) . This is entirely free there is no requirement to have paid membership of PhUSE to do this.
:*      Add your comments to the discussion page.
+
#*      Add your comments to the discussion page.
:*      Click on the discussion tab, and then on edit.
+
#*      Click on the discussion tab, and then on edit.
 
+
#:Setting up an account and editing is relatively straightforward, but there is a tutorial [[Wiki Author Training|here]] if you would find that useful.
Setting up an account and editing is relatively straightforward, but there is a tutorial [[Wiki Author Training|here]] if you would find that useful.
+
#       We suggest keeping comments for the same section together. If your comments address a section that has no comments (or relate to several sections, please feel free to start your own section for comments.)<br />
     
+
#       We are open to comments on all aspects of the document, and that may include what isn’t there. For example, we are considering including code examples for future use and would welcome comments (or contributions on that.)
2.       We suggest keeping comments for the same section together. If your comments address a section that has no comments (or relate to several sections, please feel free to start your own section for comments.)<br />
+
# We are open to comments on all aspects of the document, and that includes suggestions for additional sections. For example, we are considering including code examples for future use and would welcome comments
 
+
(or contributions on that).
3.       We are open to comments on all aspects of the document, and that may include what isn’t there. For example, we are considering including code examples for future use and would welcome comments (or contributions on that.)
+
 +
If you are unable to post comments through the Wiki, please contact the group by email at mfoxwell@cmedresearch.com.

Revision as of 10:40, 3 June 2013

The Steering board for Good Programming Practice have released for review, a Good Programming Practice guidance document. The intention being that this can be used to define standards for coding, both between and within healthcare organisations and companies. And that It could be used directly or as a basis for more detailed or tailored requirements if needed.

Comments are open until June 30th 2013, and we will then incorporate or address these comments, and will rerelease for further review. In the longer term it is expected that the document will be revised on an ongoing basis, but we hope that it can be relatively stable by the end of 2013.

The current version of the document can be located here http://phusewiki.org/wiki/index.php?title=Good_Programming_Practice_Guidance

The preferred way to contribute comments is via the wiki as follows: Doing this ensures that your comments are shared with others during the review period, which we think would be more productive use of time.

  1. Create an account on the PhUSE wiki (if you have not already done so.) . This is entirely free there is no requirement to have paid membership of PhUSE to do this.
    • Add your comments to the discussion page.
    • Click on the discussion tab, and then on edit.
    Setting up an account and editing is relatively straightforward, but there is a tutorial here if you would find that useful.
  2. We suggest keeping comments for the same section together. If your comments address a section that has no comments (or relate to several sections, please feel free to start your own section for comments.)
  3. We are open to comments on all aspects of the document, and that may include what isn’t there. For example, we are considering including code examples for future use and would welcome comments (or contributions on that.)
  4. We are open to comments on all aspects of the document, and that includes suggestions for additional sections. For example, we are considering including code examples for future use and would welcome comments

(or contributions on that).

If you are unable to post comments through the Wiki, please contact the group by email at mfoxwell@cmedresearch.com.