VIF supplies structured profile and responder-relevant information through an API. Nexgen requests that information and determines how it is mapped, stored, and displayed in its own system.
Request and response
Nexgen sends an authorized request with the agreed account, address, or profile identifier.
VIF searches its registry for a matching account or profile.
VIF returns a status indicating whether an account was found.
When a match exists, VIF returns associated profile information and responder-relevant answers in JSON.
Nexgen reads the response using its configured field mappings and display rules.
Read the response
Response item | Meaning in the supplied example |
|---|---|
| The API request completed successfully. |
| A matching account with issues to report to the dispatcher was located. |
| Profile records returned by VIF. |
| Profile details within each record. |
| Conditions, accommodations, or other responder-relevant information. |
Depending on available information, profile details can include identity information, contacts, guardian, address, physical-identification information, profile identifiers, organization, first-responder access status, and a profile-document link.
Null or empty optional values do not automatically indicate an interface failure. They may mean that information was not supplied or is unavailable.
Routing metadata and the Nexgen limitation
Answers include sequence for intended ordering or grouping, and EMS/Fire/Police indicators for responder disciplines authorized to receive the answer.
The source explicitly states that this routing-metadata feature is not yet available in Nexgen. Returned indicators must not be treated as proof that Nexgen currently applies discipline-specific presentation rules.
Organization-specific API mapping
VIF staff establishes a default mapping during setup. Each organization can include or exclude script-derived items for its use case.
Depending on configuration, API Mapping can identify transmission sequence, reporting agencies, transmitted label/value, source script question and answer, and organization-specific prompts or presentation information.
Two organizations with similar profiles can return different script information. Validate against the specific organization's approved mapping, rather than assuming the default applies universally.
These documents do not provide endpoint URLs, authentication instructions, complete schemas, or all possible status/error codes.
Still need help?
Contact us