ImageTrend Integration / CAD Push

AngelTrack's CAD push system can send trip data to ImageTrend, for situations where your crews must complete their charts inside ImageTrend rather than in AngelTrack.

ImageTrend Signup and Configuration

To use AngelTrack's ImageTrend integration, you must have an account in the ImageTrend platform. Your state department of health's EMS office will probably provide this for you.

Once your ImageTrend account is provisioned, you must input your credential into AngelTrack by visiting the "CAD Push Configuration" item under Settings, for which you must have Administrator or Captain access in AngelTrack.

The configuration settings are:

  1. Upload URL

    This is the URL of the ImageTrend webservice, to which AngelTrack will send data. There are several choices here, because this integration uses AngelTrack's CAD Push system which is also used by other integrations. ImageTrend will provide you with the upload URL; it will end with "apiservice.asmx".

  2. Token

    ImageTrend will issue this to you. It acts as your username and password.

  3. NEMSIS version

    This is the PCR data version expected by ImageTrend. Presently, ImageTrend wishes to receive v3.5.0.

  4. License number

    If you must send a License Number value in dAgency.01 other than your state license number, specify it here; else leave it blank.

  5. Agency number

    If you must send an Agency Number value in dAgency.02 other than your state trauma registry number, specify it here; else leave it blank.

Once this configuration is done, everything else will happen automatically.

Upload Prerequisites

AngelTrack will send a call to ImageTrend only if all these conditions are met:

  • The dispatch is open (not yet closed or cancelled) and has activated;
  • The dispatch is assigned to an active shift -- not to an affiliate or to a scheduled shift; and
  • The crew has at least gone enroute.

No other dispatches are reportable to ImageTrend.

Limitations

The AngelTrack-ImageTrend integration has the following limitations:

One-way data flow

Data flows from AngelTrack to ImageTrend, but does not flow back into AngelTrack's PCR. Therefore, if you use AngelTrack's QA review system, trauma registry uploader, or billing system, then your crews must create the necessary PCR records in AngelTrack, duplicating the data they input into ImageTrend.

Other integrations ineligible

This integration makes use of AngelTrack's CAD Push system, which means that these other integrations cannot also run:

Included and omitted data

When AngelTrack uploads trip data to ImageTrend, the following data is sent:

  1. Trip purpose data (complaint, priority, service, etc.)
  2. Origin and destination addresses
  3. Patient demographics and billing data
  4. Payment arrangements
  5. Crew member list with patch numbers and levels
  6. Time punches and crew GPS positions
  7. Odometer readings

Electronic signatures are not included, nor is any other PCR data. The AngelTrack-ImageTrend integration envisions that crews will do all other PCR bookkeeping in the ImageTrend portal.