You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Instructions to IHE authors on requesting changes to the FormatCode vocabulary
11
+
With the publication of the IHE FormatCode Implementation Guide (this content), the formal management of the IHE authored FormatCode vocabulary has moved. The previous wiki page is no longer formal, and will be retired.
12
+
13
+
Acceptable Changes:
14
+
* Creation of a new code -- even experimental codes can be added. However the intention would be that the new code is intended to be a normative code. Thus please do not propose the addition of temporary, or project specific codes. The codes published here are formal publication of IHE.
15
+
* Update of a code description
16
+
* note that once a code has been used it must go through the proper code lifecycle. If a committee needs a code changed, this is accomplished by deprecating the old one and creating a new one
17
+
* Deprecating a code
18
+
19
+
1. The committee that is requesting the change must hve formal governance approval for the change.
20
+
2. The committee designated author (anyone with the authority of the committee) will prepare a GIT "Pull-Request"
21
+
a. Edit the codesystem-formatcode.xml to add your new concepts
22
+
b. Edit the codesystem-formatcode.xml date to the date of your edit
23
+
c. Edit the provenance-IHE-formatcode.codesystem.xml to add a new Provenance record explaining the can
24
+
* Indicate the dates of the change
25
+
* Indicate the reason for the change
26
+
* Indicate who the committee designated author is
27
+
* Indicate what domain is the custodian of that code
28
+
d. Edit the implementationguide-IHE.FormatCode.xml to update the date of this change, and version increment
29
+
30
+
If you have any problems, or need assistance contact JohnMoehrke@gmail.com or the assigned Librian of the FormatCode IG.
31
+
32
+
# TODO
7
33
* formal approval of this publication system (IG vs the wiki)
8
-
* publish on IHE http://profiles.ihe.net/publications/FormatCode
34
+
* publish on IHE http://profiles.ihe.net/ITI/FormatCode
IHE co-chairs must follow the instructions for submitting change to the IHE FormatCode vocabulary as documented on the <ahref="https://github.com/IHE/FormatCode">IHE GitHub repository for this FormatCode implementation guide</a>.</p>
Copy file name to clipboardExpand all lines: input/pagecontent/index.xml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
<aname="intro"> </a>
4
4
<h3>Introduction</h3>
5
5
<p>
6
-
This Implementation Guide publishes the IHE vocabulary for FormatCode and the IHE managed ValueSet for FormatCode
6
+
This Implementation Guide publishes the IHE vocabulary for FormatCode and the IHE managed ValueSet for FormatCode. Given that the FormatCode is contriuted to by many IHE domains, this IG is dedicated to the publication and management of the FormatCode vocabulary.
7
7
</p>
8
8
<aname="technical"> </a>
9
9
<h3>Technical Overview</h3>
@@ -32,4 +32,4 @@
32
32
The source code for this Implementation Guide can be found on <ahref="https://github.com/IHE/FormatCode">IHE GitHub repository for FormatCode</a>
0 commit comments