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
1. The committee that is requesting the change must hve formal governance approval for the change.
22
+
1. The committee that is requesting the change must have formal governance approval for the change.
23
23
2. Create an Issue identifying the need for the change
24
-
3. The committee designated author (anyone with the authority of the committee) will prepare a GIT "Pull-Request"
25
-
4. Edit the codesystem-formatcode.xml
24
+
3. The committee designated author (anyone with the authority of the committee) will prepare a Github "Pull-Request" by creating a branch. The subsequent steps will occur within your branch.
25
+
4. Edit the codesystem-formatcode.xml
26
26
* to add your new concepts, within your domain group
27
-
* update .date to the date of your edit
28
-
5. Edit the Bundle-history-IHE-formatcode.codesystem.xml to add a new Provenance record explaining the change
29
-
* Indicate the dates of the change
30
-
* Indicate the reason for the change, be specific but keep to a sentence. might include CP number if you want.
27
+
* update CodeSystem.date to the date of your edit
28
+
5. Edit the Bundle-history-IHE-formatcode.codesystem.xml to add a new Provenance record explaining the change. Within the new entry:
29
+
* Indicate the dates of the change - YYYY, MM, and DD represent the year, month and date of the change (always 4-digit, and 2-digit, respectively)
30
+
* The fullUrl is in the format "urn:oid:1.3.6.1.4.1.19376.1.2.3.1.YYYYMMDD"
31
+
* The value of Provenance.id is in the format "formatcode-provenance-YYYYMMDD"
32
+
* The value of Provenance.occuredPeriod.end is in the format "YYYY-MM-DD"
33
+
* The value of Provenance.recorded is in the format "YYYY-MM-DDT13:00:00.0000Z"
34
+
* Indicate the reason for the change, be specific but keep to a sentence. Might include CP number if you want.
31
35
* Indicate who the committee designated author is
32
-
* Indicate what domain is the custodian of that code
33
-
6. Edit the implementationguide-IHE.FormatCode.xml to update the date of this change, and version increment
34
-
7. Create a Pull-Request with your changes and indicate that it closes your new Issue.
36
+
* Indicate what domain is the custodian of that code
37
+
6. Edit the implementationguide-IHE.FormatCode.xml to update the ImplementationGuide.date of this change, and increment ImplementationGuide.version
38
+
7. Create a Pull-Request with the branch containing your changes and indicate that it closes your new Issue.
35
39
36
-
If you have any problems, or need assistance contact JohnMoehrke@gmail.com or the assigned Liberian of the FormatCode IG.
40
+
If you have any problems, or need assistance contact JohnMoehrke@gmail.com or the assigned Librarian of the FormatCode IG.
37
41
38
42
# TODO
39
43
@@ -48,7 +52,7 @@ If you have any problems, or need assistance contact JohnMoehrke@gmail.com or th
48
52
* Get all domain FormatCodes included
49
53
* Include as comment the CDA template associated with the FormatCode
50
54
* publish on IHE http://profiles.ihe.net/ITI/FormatCode
51
-
* get canonical URI http://ihe.net/fhir/ihe.formatcode.fhir/CodeSystem/formatcode redirected for HTML mime-type to http://profiles.ihe.net/ITI/FormatCode
55
+
* get canonical URI `http://ihe.net/fhir/ihe.formatcode.fhir/CodeSystem/formatcode` redirected for HTML mime-type to http://profiles.ihe.net/ITI/FormatCode
52
56
* update the IHE wiki page to indicate the change of policy
53
57
* update the IHE wiki where other pages point at the FormatCode wiki page (such as on the XDS profile page)
54
58
* Added in to the ValueSet the codeSystem from HL7 with their codes
Copy file name to clipboardExpand all lines: input/resources/codesystem-formatcode.xml
+32-2Lines changed: 32 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ The actual list of codes is intended to be extensible.
26
26
<titlevalue="IHE Format Code set for use with Document Sharing"/>
27
27
<statusvalue="active"/>
28
28
<experimentalvalue="false"/>
29
-
<datevalue="2020-07-23" />
29
+
<datevalue="2021-03-09" />
30
30
<publishervalue="IHE"/>
31
31
<contact>
32
32
<namevalue="IHE"/>
@@ -43,7 +43,7 @@ The actual list of codes is intended to be extensible.
43
43
</telecom>
44
44
</contact>
45
45
46
-
<description value="The [IHE](http://www.ihe.net) FormatCode code system with cannical URI of http://ihe.net/fhir/ihe.formatcode.fhir/CodeSystem/formatcode is defined to be the set of [FormatCode(s) define by IHE] (http://wiki.ihe.net/index.php?title=IHE_Format_Codes), for use with [Document Sharing](https://wiki.ihe.net/index.php/Category:DocShare). This code set additionally includes, as deprecated, format codes defined by [HL7 for some Implementation Guides](http://wiki.hl7.org/index.php?title=CDA_Format_Codes_for_IHE_XDS). The HL7 codes are now managed by HL7. The set of IHE FormatCode codes was listed in HITSP C80 Table 2-153 Format Code Value Set Definition, but since has been updated. The use of the FormatCode specifies the technical format of the document. The FormatCode tends to reference the IHE Content Profile (Implementation Guide) that defines the use-case and constraints. The FormatCode is a further specialization more detailed than the mime-type. The FormatCode provides sufficient metadata information to allow any potential document content consumer to know if it can process and/or display by identifying a document encoding, structure and template. The set of codes is intended to be extensible."/>
46
+
<description value="The [IHE](http://www.ihe.net) FormatCode code system with canonical URI of http://ihe.net/fhir/ihe.formatcode.fhir/CodeSystem/formatcode is defined to be the set of [FormatCode(s) define by IHE] (http://wiki.ihe.net/index.php?title=IHE_Format_Codes), for use with [Document Sharing](https://wiki.ihe.net/index.php/Category:DocShare). This code set additionally includes, as deprecated, format codes defined by [HL7 for some Implementation Guides](http://wiki.hl7.org/index.php?title=CDA_Format_Codes_for_IHE_XDS). The HL7 codes are now managed by HL7. The set of IHE FormatCode codes was listed in HITSP C80 Table 2-153 Format Code Value Set Definition, but since has been updated. The use of the FormatCode specifies the technical format of the document. The FormatCode tends to reference the IHE Content Profile (Implementation Guide) that defines the use-case and constraints. The FormatCode is a further specialization more detailed than the mime-type. The FormatCode provides sufficient metadata information to allow any potential document content consumer to know if it can process and/or display by identifying a document encoding, structure and template. The set of codes is intended to be extensible."/>
@@ -285,6 +285,36 @@ The actual list of codes is intended to be extensible.
285
285
<!-- Note: The template ID is taken from the HL7 IPS and this document is a version of HL7’s CDA International Patient Summary. This is an HL7 template that builds on the 2018 HL7 IPS and a collaborative document that reflects the updated items that will be harmonized. -->
286
286
</property>
287
287
</concept>
288
+
<concept>
289
+
<codevalue="urn:ihe:pcc:360x:hl7:OMG:O19:2017"/>
290
+
<displayvalue="PCC 360X Referral Request"/>
291
+
<definitionvalue="HL7v2 OMG^O19 message used for 360X referral request" />
292
+
</concept>
293
+
<concept>
294
+
<codevalue="urn:ihe:pcc:360x:hl7:OSU:O51:2017"/>
295
+
<displayvalue="PCC 360X Referral Status Update"/>
296
+
<definitionvalue="HL7v2 OSU^O51 message used for 360X referral status" />
0 commit comments