|
Q: What is NEMSIS?
A: NEMSIS stands for National EMS Information System initiative. It
is a project started by the National Association of State EMS Directors to
create the framework for a national EMS dataset to be used for research
functions. Details of this project can be found at www.nemsis.org.
Q: What is the NHTSA
dataset?
A: The NHTSA dataset is the dataset adopted by the National Highway
Transportation Safety Administration. NHTSA has adopted the recommendations
of the NEMSIS project for the content of a national EMS data set. There are
over 400 data elements in the NHTSA 2.2 dataset. The NHTSA dataset standard
also defines a standard XML format for the transmission of this data between
systems.
Q: What are the data
elements?
A: The data elements describe specific pieces of data that should be
considered for collection on the local, state and national level. Only a
small percentage of the elements will be collected on the national level.
The model for data collection relies on a larger group of data elements
captured at the local level. A portion of those elements would be uploaded
to the state level, and in turn, the state would upload the national
elements into the national database.
Q: If the NHTSA
dataset is a national dataset, doesn’t that mean all states will gather the
same data?
A: No. States are allowed to choose which elements they wish to
collect. States are also allowed to add data elements to meet regional
needs. A state in a northern climate may have a need to collect data about
snowmobile accidents. The state may extend the NHTSA dataset to support that
data need.
Q: Are Ortivus North
America (NA) software products NEMSIS Compliant?
A: The National Association of State EMS Directors is still setting
rules for what NEMSIS compliant actually means. Until those rules are
finalized, it would be premature to claim compliancy. Additionally, since
states may extend the NHTSA dataset, there is no guarantee that software
that is NEMSIS Compliant guarantees acceptance of data by a state.
Q: How do Ortivus NA
products fit into this new data collection system?
A: Ortivus NA and its predecessor, Sweet Computers, have provided
data collection systems to customers for over ten years through our Runsheet
modules. Presently, we are implementing NHTSA data elements as states
require them in their state datasets. This allows the data to be captured in
our Sweet-Field Data product, then uploaded to Sweet-Billing/Station.
Sweet-Billing/Station can then export this data through a runsheet module
into the NHTSA XML format for upload to the state.
Q: My state provides a
web interface for us to input the data into the state database. Can I import
that data into Sweet-Billing?
A: This data can only be imported if the data can be exported from
the state database in the Sweet-Billing flat-file ASCII layout.
Q: Does Ortivus NA
plan to support the NHTSA XML format?
A: Ortivus NA supports the XML format for exporting data from the
Sweet-Billing database for submission of runsheet data to state databases,
but at this time, has no plans to import data into the Sweet-Billing
database in this format.
Q: My state is going
to implement a data collection program based on NEMSIS. What should I do?
A: Contact your
Ortivus NA Sales Representative to ensure your state plans have been
communicated to the Ortivus NA EDI department. Since each state can specify
its own requirements for a data collection system, development of a new
runsheet may be required, which requires time. The sooner Ortivus NA is
aware of the plans for data collection in your state, the quicker the
response.
|
