PSTA Releases New Reports, Adds Working Groups
Thursday, December 05, 2019 | Comments

The Public Safety Technology Alliance (PSTA) released two new reports and added two working groups.

The situational awareness technical subcommittee report includes initial PSTA recommendations for public safety and industry. The subcommittee recommended a common set of standard application programming interfaces (APIs) and interface structures that will make the situational awareness construct for public-safety users easier to implement and integrate into existing systems.

The PSTA board recommended a common language and symbology to ensure that all public-safety users are able to consistently identify key landmarks and information across platforms. PSTA also recommended the use of open geospatial data standards, the National Information Exchange Model (NIEM) in establishing a common naming convention schema across public safety, and the use of project open data to address a common set of open standard metadata data sets and APIs for use by both federal and state agencies.

“We have worked hard to ensure that ongoing situational awareness becomes integrated into public-safety operations now that public safety has come to expect high speed access to reliable and resilient public-safety broadband,” said David Fritsche, PSTA Situational Awareness Subcommittee chair and Secured Communications chief technology officer (CTO).

PSTA also released the mapping technical subcommittee report with a set of recommendations for a number of public-safety workflow areas surrounding existing open standards and industry-specific standards that have been field tested and adopted by organizations and vendors from across public-safety industries.

The mapping subcommittee reviewed current mapping standards and trends in public-safety mapping technology. Members identified gaps and overlapping or conflicting standards that may create potential problems for public-safety agencies using mapping solutions to provide the framework for connecting, managing, and sharing internet of things (IoT) data between other technology systems, both internally within agencies, and externally to share information with other public-safety stakeholders.

Where the desired criteria have not been met, recommendations are given regarding standards, explaining how subsequent implementation would solve a known interoperability challenge.

The group also created two new technical subcommittees, one for EMS patient care records and one for video management.

The EMS patient care records subcommittee will review existing standards and provide recommendations to help ensure a common set of open-standard HIPAA-compliant interfaces are adopted for sharing patient data across various technology systems used by EMS and hospitals including hospital electronic health records (EHR).

Many of the systems that generate and receive patient information today are siloed and proprietary, precluding the ability of medical practitioners to quickly and effectively share patient data across systems.

The video management subcommittee will review existing standards and provide recommendations for a common set of standards for real-time public-safety video communications. The initial public-safety use cases include telemedicine between EMS and hospitals, law enforcement video and unmanned aerial systems (UAS) video.

The situational awareness report is here. The mapping report is here.

Would you like to comment on the story? Find our comments system below.

Post a comment
Name: *
Email: *
Title: *
Comment: *


No Comments Submitted Yet

Be the first by using the form above to submit a comment!

Site Navigation