[Logo] NEMSIS TAC v3 Forums
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Groups] Back to home page 
[Login] Login 
XML file v3 version identifier
Forum Index » v3.5.0 - XML/XSD Structure
Author Message
kjacobson


Joined: 03/28/2012 09:46:17
Messages: 251
Offline

Request to add a way to determine what version of NEMSIS v3 an XML file is created. This way vendors, states, and other organizations can determine what file is being submitted and use accordingly. The implementation can be one of two ways:

1. It can either be an attribute of the top data element:
a. Example
i. <DEMDataSet xmlns="http://www.nemsis.org" xmlns: xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.nemsis.org
C:\Users\esparzajx\Desktop\NEMSIS_XSDs_v3.3.4.140328\NEMSIS_Xsds_v3.3.4.140328\DEMDataSet_v3.xsd" Version="3.3.4">
<dState>
<dState.01 TIMESTAMP="0000-00-00T00:00:00.0+00:00">String</dState.01>
</dState>

ii. This attribute would be mandatory in each file.
iii. It would be in the DEMDataSet or EMSDataSet tags


2. Or it can be an element.
a. Example
i. <EMSDataSet xmlns="http://www.nemsis.org" xmlns: xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.nemsis.org
C:\Users\esparzajx\Desktop\NEMSIS_XSDs_v3.3.4.140328\NEMSIS_Xsds_v3.3.4.140328\EMSDataSet_v3.xsd" >
<Version>3.3.4</Version>
<eState>
<eState.01 TIMESTAMP="0000-00-00T00:00:00.0+00:00">String</eState.01>
</eState>

ii. This would be a mandatory element
iii. It would be in the DEMDataSet or EMSDataSet tags


Please provide feedback on preferences.

This message was edited 4 times. Last update was at 06/26/2014 16:42:42

jrobertson


Joined: 10/17/2012 06:42:38
Messages: 28
Offline

The easiest would probably be as an attribute, the clearest would probably be as a separate element.

Either way, but this addition is really necessary for States receiving and processing NEMSIS v3 data.
jlegler


Joined: 03/13/2012 09:24:35
Messages: 93
Offline

It's redundant with the schemaLocation attribute, but I can see the convenience of having it as its own attribute. And, it could then be made mandatory (schemaLocation is not mandatory). It could also be helpful in cases where one wants to validate the document against a newer or older version of the standard while still retaining information about the version under which it was originally created. That being said, a single document could contain multiple records (e.g., PCRs), each of which was originally created under a different version of NEMSIS. This would happen when states aggregate records from multiple agencies, each perhaps using a product at a different NEMSIS version level, and submits those records to the national database. In order to support that, we would need to attach the version attribute to the PatientCareReport and DemographicReport elements rather than the root level element.

I support implementing it as an attribute rather than an element.

dvanorny


Joined: 12/19/2013 13:32:41
Messages: 28
Offline

We whole-heartedly agree with putting this as an attribute in the header of the XML.

On a side note, Josh -- we are not sure how it would work to combine incidents from different versions into the same file. What if the schema changed between versions, you could have a scenario where this file would not pass either version's schema or Schematron?

-Dan V (ImageTrend)
kjacobson


Joined: 03/28/2012 09:46:17
Messages: 251
Offline

From the NEMSIS TAC. The Web Service information contains the version of NEMSIS standard:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.nemsis.org/">
<soapenv:Header/>
<soapenv:Body>
<ws:SubmitDataRequest>
<ws:username>?</ws:username>
<ws:password>?</ws:password>
<ws:organization>?</ws:organization>
<ws:requestType>SubmitData</ws:requestType>
<ws:submitPayload>
<ws:payloadOfXmlElement>
XML DATA GOES HERE
</ws:payloadOfXmlElement>
</ws:submitPayload>
<ws:requestDataSchema>VERSION OF SCHEMA GOES HERE</ws:requestDataSchema>
<ws:schemaVersion>?</ws:schemaVersion>
<ws:additionalInfo>?</ws:additionalInfo>
</ws:SubmitDataRequest>
</soapenv:Body>
</soapenv:Envelope>
jburkhart


Joined: 08/28/2013 07:41:22
Messages: 1
Offline

Intermedix would also like to see this implemented. Having a quick and easy way to identify the NEMSIS version used to collect the data would be extremely useful at the state level.
 
Forum Index » v3.5.0 - XML/XSD Structure
Go to:   
Powered by JForum 2.1.9 © JForum Team