CONF-4: A ClinicalDocument/classCode element be present where the value is [CDA] “DOCCLIN” CDA HD: line 2 NEMSIS: no corresponding element CONF-5: A ClinicalDocument/moodCode element be present where the value is [CDA] “EVN” CDA HD: line 3 NEMSIS: no corresponding element The id element uniquely identifies the document. Because a revised document must have a unique id, but the same as the original, we recommend the following “setId” practice: the setId is a unique identifier for a new document, and version id is always set to The id element is then the setId concatenated with the version id, separated “1”. with a period (“.”). Example: report 12345 would have setId versioned “12345”, “1”, and id “12345.1”. CONF-6: A ClinicalDocument/setId element SHALL be present CDA HD: line 10 NEMSIS: ERecord.01 CONF-7: A ClinicalDocument/versionId element SHALL be present, and SHALL have value unless there is a “1” ClinicalDocument/relatedDocument/ParentDocument of typeCode “RPLC” CDA HD: line 11 NEMSIS: no corresponding element CONF-8: A ClinicalDocument/id element SHALL be present and SHALL have value equivalent to ClinicalDocument/setId & & ClinicalDocument/versionId “.” CDA HD: line 4 NEMSIS: no corresponding element The code element identifies the document type as an EMS Patient Care Report. This code is currently under submission to LOINC. CONF-9: A ClinicalDocument/code element SHALL be present where the value of @code is EMS Patient Care Report 2.16.840.1.113883.6.1 LOINC “EMSPCR” STATIC. CDA HD: line 5 NEMSIS: no corresponding element The title element identifies the document as a Patient Care report. The preferred title is Patient Care Report.” “EMS CONF-10: A element SHALL be present. [CDA] CDA HD: line 6 NEMSIS: no corresponding element
CONF-4: A ClinicalDocument/classCode element be present where the value is “DOCCLIN” [CDA] CDA HD: line 2 NEMSIS: no corresponding element CONF-5: A ClinicalDocument/moodCode element be present where the value is “EVN” [CDA] CDA HD: line 3 NEMSIS: no corresponding element The id element uniquely identifies the document. Because a revised document must have a unique id, but the same “setId” as the original, we recommend the following practice: the setId is a unique identifier for a new document, and version id is always set to “1”. The id element is then the setId concatenated with the version id, separated with a period (“.”). Example: report 12345 would have setId “12345”, versioned “1”, and id “12345.1”. CONF-6: A ClinicalDocument/setId element SHALL be present CDA HD: line 10 NEMSIS: ERecord.01 CONF-7: A ClinicalDocument/versionId element SHALL be present, and SHALL have value “1” unless there is a ClinicalDocument/relatedDocument/ParentDocument of typeCode “RPLC” CDA HD: line 11 NEMSIS: no corresponding element CONF-8: A ClinicalDocument/id element SHALL be present and SHALL have value equivalent to ClinicalDocument/setId & “.” & ClinicalDocument/versionId CDA HD: line 4 NEMSIS: no corresponding element The code element identifies the document type as an EMS Patient Care Report. This code is currently under submission to LOINC. CONF-9: A ClinicalDocument/code element SHALL be present where the value of @code is “EMSPCR” EMS Patient Care Report 2.16.840.1.113883.6.1 LOINC STATIC. CDA HD: line 5 NEMSIS: no corresponding element The title element identifies the document as a Patient Care report. The preferred title is “EMS Patient Care Report.” CONF-10: A element SHALL be present. [CDA] CDA HD: line 6 NEMSIS: no corresponding element