Electronic Ambulance Data Collection: API

Updated January 9, 2020. Reflects the final CMS rule, including amendments as of December 4, 2019.

The Amber API provides a way for data within Amber to be integrated with an external system. The API uses JSON to encode objects and relies on standard HTTP codes to signal operation outcomes.

The Amber API does not currently have any rate limits in place, although should usage warrant, we reserve the right to add them in the future. At this time, we do not anticipate ever restricting usage below 5 requests per second.

Amber uses simple token-based authentication. To generate or manage your API key, visit your My Account page. Your API key carries the same privileges as your user account, so be sure to keep it secret!

You authenticate to the API by providing your API key in the HTTP authorization bearer token header.

All API requests must be authenticated and made over HTTPS.

Example Using Bearer Token

$ curl https://emsamber.com/apiv1/test -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Fields

Requests and responses for Organization Info may contain one or more of the following fields:

Organization ID

Integer

org / orgid

Every organization in the system has a numeric ID. An organization may have one or more NPIs, each of which also have IDs. The Organization ID, though, is the single parent.

Example values

Year

Integer

year

Organization information may change year to year, so data also will be tagged with a four-digit year. This is the year covered by the submitted information (not the year in which it was entered).

Example values

Business Office Mailing Address Line 1

String

biz_office_mailing_address_line1

Line one (of two) of the organization's business office mailing address.

Example values

123 Anywhere Lane

61222 Ambulance Drive

Business Office Mailing Address Line 2

String

biz_office_mailing_address_line2

Line two (of two) of the organization's business office mailing address.

Example values

Suite 330

P.O. Box 81220

Business Office Mailing Address City

String

biz_office_mailing_address_city

The city of the organization's business office mailing address.

Example values

Portland

Stamford

Business Office Mailing Address State

String

biz_office_mailing_address_state

The two-letter postal abbreviation of the U.S. state of the organization's business office mailing address.

Example values

OR

CT

Business Office Mailing Address ZIP Code

String

biz_office_mailing_address_zip

The five or nine-digit postal code of the organization's business office mailing address. Numbers and an optional hyphen are accepted characters.

Example values

02162-5510

Business Office Physical Address Line 1

String

biz_office_physical_address_line1

Line one (of two) of the organization's business office physical address.

Example values

123 Anywhere Lane

61222 Ambulance Drive

Business Office Physical Address Line 2

String

biz_office_physical_address_line2

Line two (of two) of the organization's business office physical address.

Example values

Suite 330

P.O. Box 81220

Business Office Physical Address City

String

biz_office_physical_address_city

The city of the organization's business office physical address.

Example values

Portland

Stamford

Business Office Physical Address State

String

biz_office_physical_address_state

The two-letter postal abbreviation of the U.S. state of the organization's business office physical address.

Example values

OR

CT

Business Office Physical Address ZIP Code

String

biz_office_physical_address_zip

The five or nine-digit postal code of the organization's business office physical address. Numbers and an optional hyphen are accepted characters.

Example values

02162-5510

Contact First Name

String

contact_first_name

The first name of the primary CMS contact person for the organization.

Example values

Marcus

David

Contact Last Name

String

contact_last_name

The last name of the primary CMS contact person for the organization.

Example values

Roberts

Benoit

Contact Phone

String

contact_phone

The phone number of the primary CMS contact person for the organization. Because phone numbers can have weird characters (e.g., an x for extension, parentheses), allowable characters are not restricted.

Example values

(503) 555-1212

800.588.2300 x15

Contact Email

String

contact_email

The e-mail address of the primary CMS contact person for the organization.

Example values

reporter@myambulance.com

ilovecms@purplemedics.org

Name of Responsible Person

String

responsible_person_name

The name of the person responsible for the accuracy and completion of the data.

Example values

Suzie Bigcheese

Stefan Headexec

Name of Person Completing Form

String

form_completer_name

The name of the person actually filling out the information on the form/website/application.

Example values

Tom Administrator

Jessica Mellon

Organization Total Revenues

Number

org_total_rev

The total revenues for the whole organization for the year. Can be integer or float. Characters other than 0-9 and . (like, say, a comma or a dollar-sign) are not allowed.

Example values

1553603.84

Organization Total Ground Transports

Integer

grd_amb_transports_wholeorg

The total number of ground ambulance transports for the whole organization for the year. Characters other than 0-9 (like, say, a comma) are not allowed.

Example values

List records

To list records related to Organization Info, issue a GET request to the Organization Info endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/orginfo?org=1&year=2018" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":[
      {
         "orgid":1,
         "year":2018,
         "biz_office_mailing_address_line1":"1234 Anywhere Ln"
      },
      {
         "orgid":1,
         "year":2018,
         "biz_office_mailing_address_line2":"Suite 235"
      },
      {
         "orgid":1,
         "year":2018,
         "biz_office_mailing_address_city":"Peoria"
      },
      {
         "orgid":1,
         "year":2018,
         "biz_office_mailing_address_state":"KS"
      },
      {
         "orgid":1,
         "year":2018,
         "biz_office_mailing_address_zip":"12345"
      },
      {
         "orgid":1,
         "year":2018,
         "contact_first_name":"Laverne"
      },
      {
         "orgid":1,
         "year":2018,
         "contact_phone":"422-555-1212"
      },
      {
         "orgid":1,
         "year":2018,
         "contact_email":"contactperson@peoria.com"
      },
      {
         "orgid":1,
         "year":2018,
         "responsible_person_name":"Irresponsible Person"
      },
      {
         "orgid":1,
         "year":2018,
         "form_completer_name":"Form Completers"
      }
   ]
}

Create or update records

To update Organization Info records, issue a POST request to the Organization Info endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org and year, to specify the organization being updated and the year of data being submitted. Beyond that, any combination of organization fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/orginfo -d '{"org":1,"year":2018,"biz_office_mailing_address_line1":"1234 Anywhere Wy"}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"1 field(s) updated."}

Fields

Requests and responses for NPIs may contain one or more of the following fields:

Organization ID

Integer

org / orgid

Every organization in the system has a numeric ID. An organization may have one or more NPIs, each of which also have IDs. The Organization ID, though, is the single parent.

Example values

Year

Integer

year

Organization information may change year to year, so data also will be tagged with a four-digit year. This is the year covered by the submitted information (not the year in which it was entered).

Example values

NPI ID

Integer

npiid

This is the internal Amber identifier for an NPI. It is an integer, and is generally way fewer than 10-digits long (though it could be). This is NOT the CMS-assigned NPI identifier; it is specific to Amber.

Example values

NPI Number

Integer

npinum

This is the CMS-assigned NPI identifier. Only numbers 0-9 are allowed.

Example values

1001529234

3337081622

Is Active

Integer (0/1)

isactive

This is a 0 or a 1 indicating whether this NPI is active for the year in question. 0 indicates not active; 1 indicates that it is active.

Example values (complete list)

Nickname

String

nickname

This is a human-readable string that helps the user identify which NPI this is (particularly helpful when an organization has multiple).

Example values

West Side NPI

Northern Border (no longer used)

List records

To list records related to NPIs, issue a GET request to the NPIs endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/npi?org=1&year=2018" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":[
      {
         "orgid":1,
         "year":2018,
         "npiid":1,
         "npinum":"123123125",
         "isactive":1,
         "nickname":"Main NPI"
      },
      {
         "orgid":1,
         "year":2018,
         "npiid":2,
         "npinum":"987987987",
         "isactive":0,
         "nickname":"Old NPI"
      }
   ]
}

Create or update records

To update NPI records, issue a POST request to the NPI endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org and year, to specify the organization being updated and the year of data being submitted. Beyond that, any combination of NPI fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/npi -d '{"org":1,"year":2018,"npiid":1,"nickname":"Really New NPI"}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"1 field(s) updated."}

Fields

Requests and responses for NPI Contacts may contain one or more of the following fields:

Organization ID

Integer

org / orgid

Every organization in the system has a numeric ID. An organization may have one or more NPIs, each of which also have IDs. The Organization ID, though, is the single parent.

Example values

Year

Integer

year

Organization information may change year to year, so data also will be tagged with a four-digit year. This is the year covered by the submitted information (not the year in which it was entered).

Example values

NPI ID

Integer

npiid

This is the internal Amber identifier for an NPI. It is an integer, and is generally way fewer than 10-digits long (though it could be). This is NOT the CMS-assigned NPI identifier; it is specific to Amber.

Example values

Contact First Name

String

contact_first_name

The first name of the primary CMS contact person for this NPI.

Example values

Marcus

David

Contact Last Name

String

contact_last_name

The last name of the primary CMS contact person for this NPI.

Example values

Roberts

Benoit

Contact Title

String

contact_title

The title of the primary CMS contact person for this NPI.

Example values

Chief Reporter

Medical Director

Contact Phone

String

contact_phone

The phone number of the primary CMS contact person for this NPI. Because phone numbers can have weird characters (e.g., an x for extension, parentheses), allowable characters are not restricted.

Example values

(503) 555-1212

800.588.2300 x15

Contact Email

String

contact_email

The e-mail address of the primary CMS contact person for this NPI.

Example values

reporter@myambulance.com

ilovecms@purplemedics.org

Operating Organization

String

operating_org

The name of the organization that operates this NPI.

Example values

Healthy Ambulance, Inc.

Purple Transport LLC

List records

To list records related to NPI Contacts, issue a GET request to the NPI Contacts endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

npiidintegeroptional

The Amber NPI identifier of the NPI whose data you want. If you omit the npiid, all NPIs' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/npicontacts?org=1&year=2018&npiid=1" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":[
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "contact_first_name":"Lynne"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "contact_last_name":"Thigpen"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "contact_phone":"345-555-1212"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "contact_email":"npicontact@chicago.com"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "contact_title":"Muckety-Muck"
      }
   ]
}

Create or update records

To update NPI Contact records, issue a POST request to the NPI Contact endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org, npiid, and year, to specify the organization being updated, the NPI being updated, and the year of data being submitted. Beyond that, any combination of contact fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/npicontacts -d '{"org":1,"year":2018,"npiid":1,"contact_first_name":"Merc","contact_last_name":"Lapidus"}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"1 field(s) updated."}

Fields

Requests and responses for NPI Profile may contain one or more of the following fields:

Do Paramedic Intercepts?

Integer (binary)

do_intercepts

This is a binary indication of whether this NPI is a NY State-based volunteer entity that does paramedic intercepts. It's either 0 (does not perform) or 1 (performs).

Example values (complete list)

Number of Paramedic Intercepts

Integer

num_pi_responses

For volunteer services in New York State only, the total number of paramedic intercepts performed.

Example values

Other Joint Responses?

Integer (binary)

other_joint_response

This is a binary indication of whether this NPI ever deploys ALS response staff as a joint response to meet a BLS ambulance from another organization (not including paramedic intercepts as described above). It's either 0 (does not deploy) or 1 (deploys).

Example values (complete list)

Other Joint Responses

Integer

num_other_joint_responses

Other than NY-based paramedic intercepts as defined above, the number of ALS joint responses to meet a BLS ambulance from another organization.

Example values

Respond with Other Non-Transporting Agency

String (fixed options)

response_with_other

Whether the organization responds to calls with another non-transporting agency (e.g., fire).

Example values (complete list)

no

yes

Number of Responses Including Non-Transport Agency

Number

num_resp_with_other

Of all the ground ambulance responses provided (with or without transport), the number that included another non-transporting agency. Can be integer or float, but characters other than 0-9 and . are not allowed.

Example values

61.3

Type of Labor Provided By Non-Transporting Agency

String (comma-separated list of fixed options)

nonresp_labor_type

These are the types of labor provided by the non-transporting agency. The result is a comma separated list of zero to multiple entries.

These entries can be: paramedic (Paramedic), otheremt (Other EMT), or other (Other).

Example values

paramedic

paramedic,other

Other Type of Labor Provided by Non-Transporting Agency

String

nonresp_labor_type_other

If 'other' was one of the options submitted in the prior field (nonresp_labor_type), then this is the other type of labor they provide.

Example values

Main Base

Dispatch Center

Percent of Responses Where Non-Transport Agency Provides Medical Care During Transport

Number

pct_with_ongoing_medcare_by_other

Of all the ground ambulance responses provided (with or without transport), the percentage that included another non-transporting agency providing continuing medical care in the ambulance during transport. Can be integer or float, but characters other than 0-9 and . are not allowed.

Example values

61.3

Definition of Response Time

String (fixed options)

resp_time_def

This is how the NPI defines "response time." The options are calltoarrival (From when the call comes in to when the vehicle arrives on scene), leavetoarrival (From when the vehicle leaves the station to when it arrives on scene), or other (Other).

Example values (complete list)

calltoarrival

leavetoarrival

other

Other Definition of Response Time

String

resp_time_other

If 'other' was the option submitted in the prior field (resp_time_def), then this is the other type of response time definition they use.

Example values

Main Base

Dispatch Center

Response Time Measured?

String (fixed options)

measure_responsetime

This is whether the response time (as defined by the NPI) is measured. The options are yes (Is Measured) or no (Not Measured).

Example values (complete list)

yes

no

Response Time Targets

String (fixed options)

meet_responsetime_targets

Whether the organization is required or incentivised to meet response time targets, and if so, how those are set (internally, by a local municipality, by the county, or by another entity).

Example values (complete list)

no

yesbyorg

yesbymuni

yesbycounty

yesbyother

Response Time Penalties

String (fixed options)

responsetime_penalties

If an organization is required or incentivised to meet response time targets, whether or not they are penalized (through reduced payments, fines, etc) for exceeding the targets.

Example values (complete list)

no

yes

Urban In-Service Mileage

Number

totmileage_urban

Total ground ambulance in-service mileage in an Urban area. Can be integer or float, but characters other than 0-9 and . are not allowed.

Example values

61889.3

Rural In-Service Mileage

Number

totmileage_rural

Total ground ambulance in-service mileage in a Rural area. Can be integer or float, but characters other than 0-9 and . are not allowed.

Example values

61889.3

Super-Rural In-Service Mileage

Number

totmileage_superrural

Total ground ambulance in-service mileage in a Super-Rural area. Can be integer or float, but characters other than 0-9 and . are not allowed.

Example values

61889.3

List records

To list records related to NPI Profile, issue a GET request to the NPI Profile endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

npiidintegeroptional

The Amber NPI identifier of the NPI whose data you want. If you omit the npiid, all NPIs' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/npiprofile?org=1&year=2018&npiid=1" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":[
      {
         "orgid":1,
         "year":2018,
         "grd_amb_transports":"22"
      },
      {
         "orgid":1,
         "year":2018,
         "grd_amb_nontransports":"233"
      },
      {
         "orgid":1,
         "year":2018,
         "grd_amb_nontransports_pct_onsite_treatment":"39"
      },
      {
         "orgid":1,
         "year":2018,
         "meet_responsetime_targets":"yesbyorg"
      },
      {
         "orgid":1,
         "year":2018,
         "responsetime_penalties":"no"
      },
      {
         "orgid":1,
         "year":2018,
         "totmileage_urban":"5000"
      },
      {
         "orgid":1,
         "year":2018,
         "totmileage_rural":"4000"
      },
      {
         "orgid":1,
         "year":2018,
         "totmileage_superrural":"3000"
      },
      {
         "orgid":1,
         "year":2018,
         "grd_amb_total_responses_sec_area":"11"
      },
      {
         "orgid":1,
         "year":2018,
         "num_pd_transports":"1234"
      },
      {
         "orgid":1,
         "year":2018,
         "num_pi_responses":"43"
      },
      {
         "orgid":1,
         "year":2018,
         "num_other_joint_responses":"2345"
      },
      {
         "orgid":1,
         "year":2018,
         "org_total_rev":"99999"
      },
      {
         "orgid":1,
         "year":2018,
         "911_total_resp":"11"
      }
   ]
}

Create or update records

To update NPI Profile records, issue a POST request to the NPI Profile endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org, npiid, and year, to specify the organization being updated, the NPI being updated, and the year of data being submitted. Beyond that, any combination of contact fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/npiprofile -d '{"org":1,"year":2018,"npiid":1,"num_other_joint_responses":3328}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"1 field(s) updated."}

Fields

Requests and responses for NPI Characteristics may contain one or more of the following fields:

Organization ID

Integer

org / orgid

Every organization in the system has a numeric ID. An organization may have one or more NPIs, each of which also have IDs. The Organization ID, though, is the single parent.

Example values

Year

Integer

year

Organization information may change year to year, so data also will be tagged with a four-digit year. This is the year covered by the submitted information (not the year in which it was entered).

Example values

NPI ID

Integer

npiid

This is the internal Amber identifier for an NPI. It is an integer, and is generally way fewer than 10-digits long (though it could be). This is NOT the CMS-assigned NPI identifier; it is specific to Amber.

Example values

Reporting Period Start Date

Date

reporting_period_start

This is the first day of the reporting year. For calendar-year reporters, it will be 20XX-01-01, but for others, it could be a different date. It's in YYYY-MM-DD format.

Example values

2019-01-01

2020-07-01

New NPI?

Integer (binary)

is_new_npi

This is a binary indication of whether this NPI is new in the reporting year. It's either 0 (not new) or 1 (new).

Example values (complete list)

Cease Operations?

Integer (binary)

did_cease_operations

This is a binary indication of whether this NPI ceased operations in the reporting year. It's either 0 (did not cease) or 1 (ceased).

Example values (complete list)

Medicare Certification Date

Date

medicare_cert_date

This is the date the NPI received Medicare certification. It's in YYYY-MM-DD format.

Example values

2010-01-01

2005-07-08

Type of Control

String (fixed options)

type_of_control

This is the type of control for this NPI. It has a fixed set of options, with three categories (Non-Profit, For-Profit, and Governmental), each having subcategories (Voluntary, Individual, Corporation, Partnership, Federal, State, County, City/Town/Municipal, Ambulance Authority, Public/Private Partnership, and Other). Not all subcategories are in each category (for instance, Government-Individual doesn't make sense). All options are listed below.

Example values (complete list)

nonprof-vol

nonprof-corp

nonprof-ambauth

nonprof-other

proprietary-individ

proprietary-corp

proprietary-part

proprietary-other

gov-fed

gov-state

gov-county

gov-city

gov-ambauth

gov-publicprivate

gov-other

Staff Deployment Model

String (fixed options)

staff_deploy_model

This is the type of staff deployment model that best describes the NPI (Static Deployment, Dynamic Deployment, or Combined Deployment). All options are listed below.

Example values (complete list)

static

dynamic

combined

Volunteer Labor?

Integer (binary)

use_vol_labor

This is a binary indication of whether this NPI used volunteer labor for any ground ambulance-related positions in the reporting year. It's either 0 (did not use) or 1 (used).

Example values (complete list)

Type of Operation

String (fixed options)

type_of_operation

This is, broadly, the type of ambulance operation that best describes the NPI (Independent [primarily EMS services], Independent [providing non-emergency], Fire Department-Based, Public Safety Department-Based, Hospital/SNF-Based, Government Stand-Alone EMS Agency, or Other). All options are listed below.

Example values (complete list)

indep_grd

indep_mix

fire

pubsafe

hospital

government

other

Shared Costs

String (comma-separated list of fixed options)

shared_costs

This is whether the ground ambulance service shared costs (e.g., building space, personnel) with any of the listed entities. The result is a comma separated list of zero to multiple entries.

These entries can be: fire (Fire department), pubsafe (Police or other public safety), hospital (Hospital/SNF), otherhealth (Other healthcare organization - non-Medicare), airamb (Air ambulance operation), or other (Other).

Example values

fire

fire,pubsafe,airamb

Ambulance Types

String (comma-separated list of fixed options)

amb_types

This is a comma separated list of zero to multiple entries indicating which types of ambulances the NPI operates.

These entries can be: ground (Land-based), water (Water-based), and/or air (Air ambulances).

Example values

ground

ground,air

Ground Response to 911?

String (fixed options)

911_model

This is one of a few options about whether this NPI routinely provides ground response to 911 calls. Options are no (No), occasional (Yes, but not around the clock), and yes (Yes, 24/7/365).

Example values (complete list)

no

occasional

yes

List records

To list records related to NPI Characteristics, issue a GET request to the NPI Characteristics endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

npiidintegeroptional

The Amber NPI identifier of the NPI whose data you want. If you omit the npiid, all NPIs' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/npicharacteristics?org=1&year=2018&npiid=1" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":[
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "medicare_cert_date":"2013-03-12"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "is_new_npi":"0"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "did_cease_operations":"0"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "type_of_control":"nonprof-corp"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "type_of_operation":"indep_mix"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "use_vol_labor":"0"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "shared_costs":"fire,pubsafe,hospital"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "reporting_period_start":"2018-09-01"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "staff_deploy_model":"static"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "amb_types":"ground"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "911_model":"no"
      }
   ]
}

Create or update records

To update NPI Characteristics records, issue a POST request to the NPI Characteristics endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org, npiid, and year, to specify the organization being updated, the NPI being updated, and the year of data being submitted. Beyond that, any combination of contact fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/npicharacteristics -d '{"org":1,"year":2018,"npiid":1,"amb_types":"ground,air"}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"1 field(s) updated."}

Fields

Requests and responses for NPI Service Area may contain one or more of the following fields:

Organization ID

Integer

org / orgid

Every organization in the system has a numeric ID. An organization may have one or more NPIs, each of which also have IDs. The Organization ID, though, is the single parent.

Example values

Year

Integer

year

Organization information may change year to year, so data also will be tagged with a four-digit year. This is the year covered by the submitted information (not the year in which it was entered).

Example values

NPI ID

Integer

npiid

This is the internal Amber identifier for an NPI. It is an integer, and is generally way fewer than 10-digits long (though it could be). This is NOT the CMS-assigned NPI identifier; it is specific to Amber.

Example values

Full States (Primary Area)

Array of Strings

primary_fullstates

This is an array of two-letter postal abbreviations for each of the full states covered in the service's primary service area. A state is included here only if the service covers the entire state. Note that because it's an array of strings, the internal double-quotes are escaped to be JSON compliant.

Example values

[\"OR\"]

[\"NV\",\"CT\"]

Partial States (Primary Area)

Array of Strings

primary_partstates

This is an array of two-letter postal abbreviations for each of the partial states covered in the service's primary service area. A state is included here only if the service covers less than the entire state. Note that because it's an array of strings, the internal double-quotes are escaped to be JSON compliant.

Example values

[\"OR\"]

[\"NV\",\"CT\"]

Partial State Polygons (Primary Area)

Object

primary_XX_polygons

For each partial state in the service's primary area, there will either by polygons or zipcodes to specify the covered portion. For each, their key contains the two-letter postal abbreviation - so, for instance, the polygons for a service's primary region in California would be primary_CA_polygons.

The value is an object denoting the polygons in GIS format. Note that because the object contains some strings, those are denoted by escaped double-quotes.

Example value

{\"type\":\"FeatureCollection\",\"features\":[{\"type\":\"Feature\",\"properties\":{},\"geometry\":{\"type\":\"Polygon\",\"coordinates\":[[[-122.86998,45.552007],[-122.913895,45.513046],[-122.859687,45.484169],[-122.82332,45.499091],[-122.839788,45.549603],[-122.86998,45.552007]]]}}]}

Partial State Polygons (Secondary Area)

Object

secondary_XX_polygons

For each partial state in the service's secondary area, there will either by polygons or zipcodes to specify the covered portion. For each, their key contains the two-letter postal abbreviation - so, for instance, the polygons for a service's secondary region in Maine would be secondary_ME_polygons.

The value is an object denoting the polygons in GIS format. Note that because the object contains some strings, those are denoted by escaped double-quotes.

Example value

{\"type\":\"FeatureCollection\",\"features\":[{\"type\":\"Feature\",\"properties\":{},\"geometry\":{\"type\":\"Polygon\",\"coordinates\":[[[-122.86998,45.552007],[-122.913895,45.513046],[-122.859687,45.484169],[-122.82332,45.499091],[-122.839788,45.549603],[-122.86998,45.552007]]]}}]}

Partial State ZIP Codes (Primary Area)

Array of Strings

primary_XX_zips

For each partial state in the service's primary area, there will either by polygons or zipcodes to specify the covered portion. For each, their key contains the two-letter postal abbreviation - so, for instance, the zipcodes for a service's primary region in California would be primary_CA_zips.

The value is an array of strings of five-digit ZIP codes covered in the state.

Example values

[\"97003\",\"97005\",\"97006\"]

[\"02101\",\"02119\",\"02131\"]

Serves Secondary Area?

Integer (binary)

servessecondaryarea

This is a binary indication of whether this NPI serves a secondary area. It's either 0 (does not serve) or 1 (does serve).

Example values (complete list)

Primary Provider in Primary Area?

String (fixed options)

primary_isprimary

This is an indication of whether the NPI is the primary emergency provider in its primary service area. Options are "yes" and "no".

Example values (complete list)

yes

no

Average Trip Time in Primary Area

String (fixed options)

primary_avgtriptime

This is the average trip time (from dispatch to available for another call) for this NPI in its primary service area. The options are under30 (Fewer than 30 minutes), 30to60 (30-60 minutes), 61to90 (61-90 minutes), 91to120 (91-120 minutes), 121to150 (121-150 minutes), or over150 (More than 150 minutes).

Example values

under30

91to120

Average Trip Time in Secondary Area

String (fixed options)

secondary_avgtriptime

This is the average trip time (from dispatch to available for another call) for this NPI in its secondary service area. The options are under30 (Fewer than 30 minutes), 30to60 (30-60 minutes), 61to90 (61-90 minutes), 91to120 (91-120 minutes), 121to150 (121-150 minutes), or over150 (More than 150 minutes).

Example values

under30

91to120

Average Response Time in Primary Area

Number

primary_avgresptime

This is the average response time (in minutes) in the NPI's primary service area. Numerals and a decimal point are allowed, but no other characters (e.g., comma).

Example values

81.5

Average Response Time in Secondary Area

Number

secondary_avgresptime

This is the average response time (in minutes) in the NPI's secondary service area. Numerals and a decimal point are allowed, but no other characters (e.g., comma).

Example values

81.5

90th Percentile Response Time in Primary Area

Number

primary_90pctileresptime

This is the response time below which 90 percent of the emergency responses fall (in minutes) in the NPI's primary service area. Numerals and a decimal point are allowed, but no other characters (e.g., comma).

Example values

81.5

List records

To list records related to NPI Service Area, issue a GET request to the NPI Service Area endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/npiservicearea?org=1&year=2018" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":[
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "primary_OR_zips":"[\"97003\",\"97005\",\"97006\",\"97078\",\"97123\",\"97124\",\"97229\"]"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "primary_partstates":"[\"NV\",\"OR\"]"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "primary_fullstates":"[\"AZ\"]"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "secondary_fullstates":"[\"WY\"]"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "secondary_partstates":"[\"OR\"]"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "primary_OR_polygons":"{\"type\":\"FeatureCollection\",\"features\":[{\"type\":\"Feature\",\"properties\":{},\"geometry\":{\"type\":\"Polygon\",\"coordinates\":[[[-122.86998,45.552007],[-122.913895,45.513046],[-122.859687,45.484169],[-122.82332,45.499091],[-122.839788,45.549603],[-122.86998,45.552007]]]}}]}"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
		 "primary_NV_polygons":"{\"type\":\"FeatureCollection\",\"features\":[{\"type\":\"Feature\",\"properties\":{},\"geometry\":{\"type\":\"Polygon\",\"coordinates\":[[[-114.830368,35.558345],[-114.995051,35.451022],[-114.720579,35.164126],[-114.665684,35.32563],[-114.830368,35.558345]]]}}]}"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "primary_NV_zips":"[\"89029\",\"89039\",\"89046\"]"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "secondary_OR_polygons":"{\"type\":\"FeatureCollection\",\"features\":[{\"type\":\"Feature\",\"properties\":{},\"geometry\":{\"type\":\"Polygon\",\"coordinates\":[[[-119.818105,42.58418],[-119.730274,42.178416],[-117.578409,42.210974],[-117.688198,42.794141],[-119.818105,42.58418]]]}}]}"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "servessecondaryarea":"1"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "primary_avgresptime":"33"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "primary_avgtriptime":"61to90"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "primary_isprimary":"yes"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "secondary_avgresptime":"333"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "secondary_avgtriptime":"91to120"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "secondary_isprimary":"no"
      }
   ]
}

Create or update records

To update NPI Service Area records, issue a POST request to the NPI Service Area endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org, npiid, and year, to specify the organization being updated, the NPI being updated, and the year of data being submitted. Beyond that, any combination of contact fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/npiservicearea -d '{"org":1,"year":2018,"npiid":1,"secondary_avgtriptime":"61to90"}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"1 field(s) updated."}

Fields

Requests and responses for NPI Service Mix may contain one or more of the following fields:

Organization ID

Integer

org / orgid

Every organization in the system has a numeric ID. An organization may have one or more NPIs, each of which also have IDs. The Organization ID, though, is the single parent.

Example values

Year

Integer

year

Organization information may change year to year, so data also will be tagged with a four-digit year. This is the year covered by the submitted information (not the year in which it was entered).

Example values

NPI ID

Integer

npiid

This is the internal Amber identifier for an NPI. It is an integer, and is generally way fewer than 10-digits long (though it could be). This is NOT the CMS-assigned NPI identifier; it is specific to Amber.

List records

To list records related to NPI Service Mix, issue a GET request to the NPI Service Mix endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

npiidintegeroptional

The Amber NPI identifier of the NPI whose data you want. If you omit the npiid, all NPIs' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/npiservicemix?org=1&year=2018&npiid=1" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":[
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "provides_long_distance":"1"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "provides_long_duration":"1"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "pays_911_fees":"1"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "pays_other_fees":"0"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "has_local_svc_standards":"1"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "pct_emer":"29"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "pct_nonemer":"71"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "pct_land":"16"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "pct_interfacility_xport":"30"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "pct_water":"84"
      }
   ]
}

Create or update records

To update NPI Service Mix records, issue a POST request to the NPI Service Mix endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org, npiid, and year, to specify the organization being updated, the NPI being updated, and the year of data being submitted. Beyond that, any combination of contact fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/npiservicemix -d '{"org":1,"year":2018,"npiid":1,"pct_interfacility_xport":"18"}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"1 field(s) updated."}

Fields

Requests and responses for Utilization Info may contain one or more of the following fields:

List records

To list records related to Utilization Info, issue a GET request to the Utilization Info endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

npiidintegeroptional

The Amber NPI identifier of the NPI whose data you want. If you omit the npiid, all NPIs' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/utilization?org=1&year=2018&npiid=1" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":[
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "fsah_deployed":"800"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "fsah_available":"1040"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "fsah_vol_on_call":"800"
      }
   ]
}

Create or update records

To update Utilization Info records, issue a POST request to the Utilization Info endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org, npiid, and year, to specify the organization being updated, the NPI being updated, and the year of data being submitted. Beyond that, any combination of contact fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/utilization -d '{"org":1,"year":2018,"npiid":1,"fsah_vol_on_call":"1277"}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"1 field(s) updated."}

Fields

Requests and responses for Medicare Utilization may contain one or more of the following fields:

Organization ID

Integer

org / orgid

Every organization in the system has a numeric ID. An organization may have one or more NPIs, each of which also have IDs. The Organization ID, though, is the single parent.

Example values

Year

Integer

year

Organization information may change year to year, so data also will be tagged with a four-digit year. This is the year covered by the submitted information (not the year in which it was entered).

Example values

NPI ID

Integer

npiid

This is the internal Amber identifier for an NPI. It is an integer, and is generally way fewer than 10-digits long (though it could be). This is NOT the CMS-assigned NPI identifier; it is specific to Amber.

Example values

Service Level (HCPCS Code)

String (fixed options)

svc_level

This is the HCPCS code for the service level being reported. The options are A0426, A0427, A0428, A0429, A0432, A0433, A0434, A0998, and A0999. More detail about HCPCS codes can be found from CMS and at https://hcpcs.codes.

Example values

A0427

A0429

Number of Urban Transports

Integer

num_urban_transports

This is the number of transports in an Urban area for the service level being reported. Only numerals 0-9 are allowed.

Example values

Number of Rural Transports

Integer

num_rural_transports

This is the number of transports in a Rural area for the service level being reported. Only numerals 0-9 are allowed.

Example values

Number of Super-Rural Transports

Integer

num_superrural_transports

This is the number of transports in a Super-Rural area for the service level being reported. Only numerals 0-9 are allowed.

Example values

Revenue

Number

revenue

This is the amount of revenue received for the service level being reported. Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., comma or dollar-sign) are not allowed.

Example values

188400.92

Mileage

Number

mileage

This is the amount of miles driven for the service level being reported. Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., comma) are not allowed.

Example values

18400.9

List records

To list records related to Medicare Utilization, issue a GET request to the Medicare Utilization endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

npiidintegeroptional

The Amber NPI identifier of the NPI whose data you want. If you omit the npiid, all NPIs' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/medicareutil?org=1&year=2018&npiid=1" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":{
      "1":{  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "svc_level":"A0426",
         "num_urban_transports":"1",
         "num_rural_transports":"2",
         "num_superrural_transports":"3",
         "revenue":"200",
         "mileage":"100"
      },
      "2":{  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "svc_level":"A0427",
         "num_urban_transports":"4",
         "num_rural_transports":"5",
         "num_superrural_transports":"6",
         "revenue":"300",
         "mileage":"400"
      },
      "3":{  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "svc_level":"A0428",
         "num_urban_transports":"7",
         "num_rural_transports":"8",
         "num_superrural_transports":"9",
         "revenue":"500",
         "mileage":"600"
      },
      "4":{  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "svc_level":"A0429",
         "num_urban_transports":"10",
         "num_rural_transports":"11",
         "num_superrural_transports":"12",
         "revenue":"700",
         "mileage":"800"
      },
      "5":{  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "svc_level":"A0432",
         "num_urban_transports":"13",
         "num_rural_transports":"14",
         "num_superrural_transports":"15",
         "revenue":"900",
         "mileage":"1000"
      },
      "6":{  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "svc_level":"A0433",
         "num_urban_transports":"16",
         "num_rural_transports":"17",
         "num_superrural_transports":"18",
         "revenue":"1100",
         "mileage":"1200"
      },
      "7":{  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "svc_level":"A0434",
         "num_urban_transports":"19",
         "num_rural_transports":"20",
         "num_superrural_transports":"21",
         "revenue":"1300",
         "mileage":"1400"
      },
      "8":{  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "svc_level":"A0998",
         "num_urban_transports":"22",
         "num_rural_transports":"23",
         "num_superrural_transports":"24",
         "revenue":"1500",
         "mileage":"1600"
      },
      "9":{  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "svc_level":"A0999",
         "num_urban_transports":"25",
         "num_rural_transports":"26",
         "num_superrural_transports":"27",
         "revenue":"1700",
         "mileage":"1800"
      }
   }
}

Create or update records

To update Medicare Utilization records, issue a POST request to the Medicare Utilization endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org, npiid, and year, to specify the organization being updated, the NPI being updated, and the year of data being submitted. Beyond that, any combination of contact fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/medicareutil -d '{"org":1,"year":2018,"npiid":3,"utildata":[{"svc_level":"A0999","revenue":1299}]}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"1 field(s) updated."}

Fields

Requests and responses for Transport Revenue may contain one or more of the following fields:

Organization ID

Integer

org / orgid

Every organization in the system has a numeric ID. An organization may have one or more NPIs, each of which also have IDs. The Organization ID, though, is the single parent.

Example values

Year

Integer

year

Organization information may change year to year, so data also will be tagged with a four-digit year. This is the year covered by the submitted information (not the year in which it was entered).

Example values

NPI ID

Integer

npiid

This is the internal Amber identifier for an NPI. It is an integer, and is generally way fewer than 10-digits long (though it could be). This is NOT the CMS-assigned NPI identifier; it is specific to Amber.

Example values

Can Report By Payer

String (fixed options)

transport_can_report_by_payer

This is an indication of whether this NPI can report transport revenue by payer. The options are either "yes" or "no". If this is no, then only the All Payers Total Rev figure will be used for transport revenue. Otherwise, the figures by source will be used.

Example values (complete list)

yes

no

All Payers Total Rev

Number

transport_allpayers_totalrev

This is the total transport revenue for this NPI, regardless of payer. It is only needed if the NPI cannot report transport revenue by payer. If transport_can_report_by_payer is yes, then this figure is ignored.

Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

81300.52

Medicare Fee for Service Total Rev

Number

transport_medicareffs_totalrev

This is the transport revenue for this NPI paid by Medicare for fee-for-service. It is only used if the NPI indicated they can report transport revenue by payer. If transport_can_report_by_payer is no, then this figure is ignored.

Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

81300.52

Medicare Advantage/Managed Care Total Rev

Number

transport_medicareadv_totalrev

This is the transport revenue for this NPI paid by Medicare Advantage/Managed Care. It is only used if the NPI indicated they can report transport revenue by payer. If transport_can_report_by_payer is no, then this figure is ignored.

Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

81300.52

Medicaid (Traditional) Total Rev

Number

transport_medicaid_totalrev

This is the transport revenue for this NPI paid by Medicaid's traditional, fee-for-service program. It is only used if the NPI indicated they can report transport revenue by payer. If transport_can_report_by_payer is no, then this figure is ignored.

Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

81300.52

Medicaid Managed Care Total Rev

Number

transport_medicaid_managedcare_totalrev

This is the transport revenue for this NPI paid by Medicaid's managed care program. It is only used if the NPI indicated they can report transport revenue by payer. If transport_can_report_by_payer is no, then this figure is ignored.

Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

81300.52

Tricare Total Rev

Number

transport_tricare_totalrev

This is the transport revenue for this NPI paid by Tricare. It is only used if the NPI indicated they can report transport revenue by payer. If transport_can_report_by_payer is no, then this figure is ignored.

Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

81300.52

VA Total Rev

Number

transport_va_totalrev

This is the transport revenue for this NPI paid by the Veterans Administration. It is only used if the NPI indicated they can report transport revenue by payer. If transport_can_report_by_payer is no, then this figure is ignored.

Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

81300.52

Commercial Insurance Total Rev

Number

transport_commercial_totalrev

This is the transport revenue for this NPI paid by commercial insurance. It is only used if the NPI indicated they can report transport revenue by payer. If transport_can_report_by_payer is no, then this figure is ignored.

Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

81300.52

Workers Comp Total Rev

Number

transport_workerscomp_totalrev

This is the transport revenue for this NPI paid by workers compensation insurance. It is only used if the NPI indicated they can report transport revenue by payer. If transport_can_report_by_payer is no, then this figure is ignored.

Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

81300.52

Self-Pay Total Rev

Number

transport_selfpay_totalrev

This is the transport revenue for this NPI paid by patient self-pay. It is only used if the NPI indicated they can report transport revenue by payer. If transport_can_report_by_payer is no, then this figure is ignored.

Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

81300.52

Medicare Fee for Service Cost Sharing?

String (fixed options)

transport_medicareffs_rev_transport_incl_costsharing

This is an indication of whether the Medicare Fee for Service revenue for this NPI includes cost sharing. The options are either "yes" or "no".

Example values (complete list)

yes

no

Medicare Advantage/Managed Care Cost Sharing?

String (fixed options)

transport_medicareadv_rev_transport_incl_costsharing

This is an indication of whether the Medicare Advantage/Managed Care revenue for this NPI includes cost sharing. The options are either "yes" or "no".

Example values (complete list)

yes

no

Medicaid (Traditional) Cost Sharing?

String (fixed options)

transport_medicaid_rev_transport_incl_costsharing

This is an indication of whether the Medicaid revenue (from the traditional, fee-for-service Medicaid program) for this NPI includes cost sharing. The options are either "yes" or "no".

Example values (complete list)

yes

no

Medicaid (Managed Care) Cost Sharing?

String (fixed options)

transport_medicaid_managedcare_rev_transport_incl_costsharing

This is an indication of whether the Medicaid Managed Care revenue for this NPI includes cost sharing. The options are either "yes" or "no".

Example values (complete list)

yes

no

Tricare Cost Sharing?

String (fixed options)

transport_tricare_rev_transport_incl_costsharing

This is an indication of whether the Tricare revenue for this NPI includes cost sharing. The options are either "yes" or "no".

Example values (complete list)

yes

no

VA Cost Sharing?

String (fixed options)

transport_va_rev_transport_incl_costsharing

This is an indication of whether the Veterans Administration revenue for this NPI includes cost sharing. The options are either "yes" or "no".

Example values (complete list)

yes

no

Commercial Insurance Cost Sharing?

String (fixed options)

transport_commercial_rev_transport_incl_costsharing

This is an indication of whether the commercial insurance revenue for this NPI includes cost sharing. The options are either "yes" or "no".

Example values (complete list)

yes

no

Workers Compensation Cost Sharing?

String (fixed options)

transport_workerscomp_rev_transport_incl_costsharing

This is an indication of whether the workers' compensation revenue for this NPI includes cost sharing. The options are either "yes" or "no".

Example values (complete list)

yes

no

Patient Self-Pay Cost Sharing?

String (fixed options)

transport_selfpay_rev_transport_incl_costsharing

This is an indication of whether the patient self-pay revenue for this NPI includes cost sharing. The options are either "yes" or "no".

Example values (complete list)

yes

no

Medicare Fee-for-Service Billing Frequency

String (fixed options)

transport_medicareffs_rev_transport_billing_freq

This is an indication of how often the NPI tried to bill Medicare Fee-for-Service for amounts owed for a transport. The options are always (Always), usually (Usually), sometimes (Sometimes), and never (Never).

Example values (complete list)

always

usually

sometimes

never

Medicare Advantage/Managed Care Billing Frequency

String (fixed options)

transport_medicareadv_rev_transport_billing_freq

This is an indication of how often the NPI tried to bill Medicare Advantage/Managed Care for amounts owed for a transport. The options are always (Always), usually (Usually), sometimes (Sometimes), and never (Never).

Example values (complete list)

always

usually

sometimes

never

Medicaid (Traditional) Billing Frequency

String (fixed options)

transport_medicaid_rev_transport_billing_freq

This is an indication of how often the NPI tried to bill Medicaid's traditional fee-for-service program for amounts owed for a transport. The options are always (Always), usually (Usually), sometimes (Sometimes), and never (Never).

Example values (complete list)

always

usually

sometimes

never

Medicaid Managed Care Billing Frequency

String (fixed options)

transport_medicaid_managedcare_rev_transport_billing_freq

This is an indication of how often the NPI tried to bill Medicaid's Managed Care program for amounts owed for a transport. The options are always (Always), usually (Usually), sometimes (Sometimes), and never (Never).

Example values (complete list)

always

usually

sometimes

never

Tricare Billing Frequency

String (fixed options)

transport_tricare_rev_transport_billing_freq

This is an indication of how often the NPI tried to bill Tricare for amounts owed for a transport. The options are always (Always), usually (Usually), sometimes (Sometimes), and never (Never).

Example values (complete list)

always

usually

sometimes

never

VA Billing Frequency

String (fixed options)

transport_va_rev_transport_billing_freq

This is an indication of how often the NPI tried to bill the Veterans Administration for amounts owed for a transport. The options are always (Always), usually (Usually), sometimes (Sometimes), and never (Never).

Example values (complete list)

always

usually

sometimes

never

Commercial Insurance Billing Frequency

String (fixed options)

transport_commercial_rev_transport_billing_freq"

This is an indication of how often the NPI tried to bill commercial insurance for amounts owed for a transport. The options are always (Always), usually (Usually), sometimes (Sometimes), and never (Never).

Example values (complete list)

always

usually

sometimes

never

Workers Comp Billing Frequency

String (fixed options)

transport_workerscomp_rev_transport_billing_freq

This is an indication of how often the NPI tried to bill workers compensation providers for amounts owed for a transport. The options are always (Always), usually (Usually), sometimes (Sometimes), and never (Never).

Example values (complete list)

always

usually

sometimes

never

Patient Self-Pay Billing Frequency

String (fixed options)

transport_selfpay_rev_transport_billing_freq

This is an indication of how often the NPI tried to bill a self-paying patient for amounts owed for a transport. The options are always (Always), usually (Usually), sometimes (Sometimes), and never (Never).

Example values (complete list)

always

usually

sometimes

never

List records

To list records related to Transport Revenue, issue a GET request to the Transport Revenue endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

npiidintegeroptional

The Amber NPI identifier of the NPI whose data you want. If you omit the npiid, all NPIs' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/transportrev?org=1&year=2018&npiid=1" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":[
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_can_report_by_payer":"yes"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_medicareffs_totalrev":"11"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_medicareffs_rev_transport_incl_costsharing":"yes"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_medicareffs_rev_transport_billing_freq":"usually"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_medicareadv_totalrev":"12"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_medicareadv_rev_transport_incl_costsharing":"no"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_medicareadv_rev_transport_billing_freq":"always"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_medicaid_totalrev":"13"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_medicaid_rev_transport_incl_costsharing":"no"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_medicaid_rev_transport_billing_freq":"always"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_tricare_totalrev":"14"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_tricare_rev_transport_incl_costsharing":"no"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_tricare_rev_transport_billing_freq":"always"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_va_totalrev":"15"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_va_rev_transport_incl_costsharing":"no"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_va_rev_transport_billing_freq":"always"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_commercial_totalrev":"16"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_commercial_rev_transport_incl_costsharing":"no"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_commercial_rev_transport_billing_freq":"always"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_workerscomp_totalrev":"17"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_workerscomp_rev_transport_incl_costsharing":"no"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_workerscomp_rev_transport_billing_freq":"always"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_selfpay_totalrev":"18"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_selfpay_rev_transport_incl_costsharing":"no"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "transport_selfpay_rev_transport_billing_freq":"always"
      }
   ]
}

Create or update records

To update Transport Revenue records, issue a POST request to the Transport Revenue endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org, npiid, and year, to specify the organization being updated, the NPI being updated, and the year of data being submitted. Beyond that, any combination of revenue fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/transportrev -d '{"org":1,"year":2018,"npiid":1,"transport_selfpay_rev_transport_incl_costsharing":"yes","transport_selfpay_rev_transport_billing_freq":"always"}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"2 field(s) updated."}

Fields

Requests and responses for Other Revenue may contain one or more of the following fields:

Organization ID

Integer

org / orgid

Every organization in the system has a numeric ID. An organization may have one or more NPIs, each of which also have IDs. The Organization ID, though, is the single parent.

Example values

Year

Integer

year

Organization information may change year to year, so data also will be tagged with a four-digit year. This is the year covered by the submitted information (not the year in which it was entered).

Example values

NPI ID

Integer

npiid

This is the internal Amber identifier for an NPI. It is an integer, and is generally way fewer than 10-digits long (though it could be). This is NOT the CMS-assigned NPI identifier; it is specific to Amber.

8250.67

List records

To list records related to Other Revenue, issue a GET request to the Other Revenue endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

npiidintegeroptional

The Amber NPI identifier of the NPI whose data you want. If you omit the npiid, all NPIs' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/otherrev?org=1&year=2018&npiid=1" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":[
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "facil_ks_totalrev":"100"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "facil_ks_rev_togrd":"90"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "subcontracts_totalrev":"200"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "subcontracts_rev_togrd":"91"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "standby_totalrev":"300"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "standby_rev_togrd":"92"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "memfees_totalrev":"400"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "memfees_rev_togrd":"93"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "charitable_donations_totalrev":"500"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "charitable_donations_rev_togrd":"94"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "exec_loans_totalrev":"600"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "exec_loans_rev_togrd":"95"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "progrelated_investments_totalrev":"700"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "progrelated_investments_rev_togrd":"96"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "local_tax_earmarks_totalrev":"800"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "local_tax_earmarks_rev_togrd":"95"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "enterprise_funds_totalrev":"900"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "enterprise_funds_rev_togrd":"94"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "asset_sales_totalrev":"1000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "asset_sales_rev_togrd":"93"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "bonds_debt_totalrev":"1100"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "bonds_debt_rev_togrd":"92"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "equip_donation_totalrev":"1120"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "equip_donation_rev_togrd":"91"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "other_donation_totalrev":"1000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "other_donation_rev_togrd":"90"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "special_grants_totalrev":"900"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "special_grants_rev_togrd":"89"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "matching_grants_totalrev":"800"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "matching_grants_rev_togrd":"90"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "tech_assistance_totalrev":"700"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "tech_assistance_rev_togrd":"95"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "demo_grants_totalrev":"600"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "demo_grants_rev_togrd":"90"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "congressional_earmarks_totalrev":"500"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "congressional_earmarks_rev_togrd":"80"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "othersource_totalrev":"400"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "othersource_rev_togrd":"85"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "shared":"650000"
      }
   ]
}

Create or update records

To update Other Revenue records, issue a POST request to the Other Revenue endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org, npiid, and year, to specify the organization being updated, the NPI being updated, and the year of data being submitted. Beyond that, any combination of revenue fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/otherrev -d '{"org":1,"year":2018,"npiid":1,"othersource_rev_togrd":95}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"1 field(s) updated."}

Fields

Requests and responses for Labor Costs may contain one or more of the following fields:

getforfree

listedelsewhere

contract

EMT-Basic Total Annual Comp

Number

labor_emtbasic_annualcomp

This is the total compensation for all paid EMT-Basic staff, including salary/wages, benefits, overtime, etc. Only numbers 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

182500.50

getforfree

listedelsewhere

contract

EMT-Intermediate Total Annual Comp

Number

labor_emtintermediate_annualcomp

This is the total compensation for all paid EMT-Intermediate staff, including salary/wages, benefits, overtime, etc. Only numbers 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

182500.50

getforfree

listedelsewhere

contract

EMT-Paramedic Total Annual Comp

Number

labor_emtparamedic_annualcomp

This is the total compensation for all paid EMT-Paramedic staff, including salary/wages, benefits, overtime, etc. Only numbers 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

182500.50

getforfree

listedelsewhere

contract

Nurse/Doctor/Other Medical Staff Total Annual Comp

Number

labor_othermedstaff_annualcomp

This is the total compensation for all paid Nurse/Doctor/Other Medical Staff staff, including salary/wages, benefits, overtime, etc. Only numbers 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

182500.50

getforfree

listedelsewhere

contract

Emergency Medical Responder (EMR) Total Annual Comp

Number

labor_emr_annualcomp

This is the total compensation for all paid Emergency Medical Responder (EMR) staff, including salary/wages, benefits, overtime, etc. Only numbers 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

182500.50

getforfree

listedelsewhere

contract

Ambulance Driver (non-EMT/EMR) Total Annual Comp

Number

labor_driver_annualcomp

This is the total compensation for all paid Ambulance Driver (non-EMT/EMR) staff, including salary/wages, benefits, overtime, etc. Only numbers 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

182500.50

getforfree

listedelsewhere

contract

Medical Director Total Annual Comp

Number

labor_meddir_annualcomp

This is the total compensation for all paid Medical Director staff, including salary/wages, benefits, overtime, etc. Only numbers 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

182500.50

getforfree

listedelsewhere

contract

Administrative Staff (e.g., HR, IT, billing) Total Annual Comp

Number

labor_admin_annualcomp

This is the total compensation for all paid Administrative Staff (e.g., HR, IT, billing) staff, including salary/wages, benefits, overtime, etc. Only numbers 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

182500.50

getforfree

listedelsewhere

contract

Management (Exec, PIO, etc) Total Annual Comp

Number

labor_management_annualcomp

This is the total compensation for all paid Management (Exec, PIO, etc) staff, including salary/wages, benefits, overtime, etc. Only numbers 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

182500.50

getforfree

listedelsewhere

contract

Dispatch/Call Center Total Annual Comp

Number

labor_dispatch_annualcomp

This is the total compensation for all paid Dispatch/Call Center staff, including salary/wages, benefits, overtime, etc. Only numbers 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

182500.50

getforfree

listedelsewhere

contract

Vehicle Maintenance Total Annual Comp

Number

labor_maintenance_annualcomp

This is the total compensation for all paid Vehicle Maintenance staff, including salary/wages, benefits, overtime, etc. Only numbers 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

182500.50

getforfree

listedelsewhere

contract

Facilities Maintenance (janitorial, laundry, etc) Total Annual Comp

Number

labor_facilities_annualcomp

This is the total compensation for all paid Facilities Maintenance (janitorial, laundry, etc) staff, including salary/wages, benefits, overtime, etc. Only numbers 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

182500.50

getforfree

listedelsewhere

contract

Other Total Annual Comp

Number

labor_other_annualcomp

This is the total compensation for all paid Other staff, including salary/wages, benefits, overtime, etc. Only numbers 0-9 and a decimal point are allowed. Other characters (e.g., dollar sign or comma) are not permitted.

Example values

182500.50

billing

qa,data

Admin Labor Costs Allocated From Parent

Number

labor_cost_admin_shared

If an organization has multiple NPIs, this is the amount of administrative labor costs allocated to this NPI from the parent organization. Organizations with only one NPI can omit this field or submit 0. Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., dollar-sign, comma) are not permitted.

Example values

8250.67

Volunteer Stipend/Benefit Costs

Number

labor_cost_vol_stipends

If an NPI has volunteers, this is the total cost of stipends, benefits, and/or honoraria for those volunteers. Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., dollar-sign, comma) are not permitted.

Example values

8250.67

List records

To list records related to Labor Costs, issue a GET request to the Labor Costs endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

npiidintegeroptional

The Amber NPI identifier of the NPI whose data you want. If you omit the npiid, all NPIs' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/laborexp?org=1&year=2018&npiid=1" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":[
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "labor_emtbasic_numpaid":"0"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "labor_emtbasic_numvol":"0"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "labor_emtbasic_whynopaidorvol":"getforfree"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "labor_emtintermediate_numpaid":"1"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "labor_emtintermediate_numvol":"2"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "labor_emtintermediate_annualcomp":"30000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "labor_emtintermediate_paidhpy":"40"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "labor_emtintermediate_totalvolhours":"60"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "labor_cost_have_paid":"billing,data,training,qa"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "labor_cost_admin_shared":"50000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "labor_cost_vol_stipends":"5000"
      }
   ]
}

Create or update records

To update Labor Cost records, issue a POST request to the Labor Cost endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org, npiid, and year, to specify the organization being updated, the NPI being updated, and the year of data being submitted. Beyond that, any combination of cost fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/laborexp -d '{"org":1,"year":2018,"npiid":1,"labor_cost_have_paid":"billing,training"}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"1 field(s) updated."}

Fields

Requests and responses for Facility Costs may contain one or more of the following fields:

Organization ID

Integer

org / orgid

Every organization in the system has a numeric ID. An organization may have one or more NPIs, each of which also have IDs. The Organization ID, though, is the single parent.

Example values

Year

Integer

year

Organization information may change year to year, so data also will be tagged with a four-digit year. This is the year covered by the submitted information (not the year in which it was entered).

Example values

NPI ID

Integer

npiid

This is the internal Amber identifier for an NPI. It is an integer, and is generally way fewer than 10-digits long (though it could be). This is NOT the CMS-assigned NPI identifier; it is specific to Amber.

Example values

Facility Name

String

cost_facil_name.#

This is a user-recognizable name for a facility. The # in the field name is an integer greater than or equal to 1, indicating the array number of the facility. The first facility entered will be 1, the next 2, and so on.

Example values

Main Base

Dispatch Center

Ownership Type

String (fixed options)

cost_facil_ownership_type.#

This is the type of ownership for a facility. The # in the field name is an integer greater than or equal to 1, indicating the array number of the facility. The first facility entered will be 1, the next 2, and so on.

Options are ownedmort (Owned with Mortgage), ownedclear (Owned Outright), rented (Rented), or donated (Donated).

Example values (complete list)

ownedmort

ownedclear

rented

donated

Square Feet

Integer

cost_facil_square_feet.#

The square footage of the facility. The # in the field name is an integer greater than or equal to 1, indicating the array number of the facility. The first facility entered will be 1, the next 2, and so on.

Example values

Annual Rental/Lease/Mortgage

Number

cost_facil_annual_cost.#

For facilities that are rented or have a mortgage, the annual cost of that rent or mortgage. The # in the field name is an integer greater than or equal to 1, indicating the array number of the facility. The first facility entered will be 1, the next 2, and so on.

Only numerals 0-9 and a decimal point are permitted. Other characters (e.g., dollar sign, comma) are not allowed.

Percent of Facility Maintenance/Improvement Costs Attributable Ground Ambulances

Number

cost_facil_maint_pct_to_grd

The percent of facility maintenance and improvement costs that were spent on ground ambulances for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas) are not permitted.

Example values

Percent of Facility Utilities Costs Attributable Ground Ambulances

Number

cost_facil_util_pct_to_grd

The percent of facility utility costs that were spent on ground ambulances for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas) are not permitted.

Example values

Percent of Facility Tax Costs Attributable Ground Ambulances

Number

cost_facil_taxes_pct_to_grd

The percent of facility tax costs (not reported elsewhere) that were spent on ground ambulances for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas) are not permitted.

Example values

Facility Costs Allocated From Parent

Number

cost_facil_shared

If an organization has multiple NPIs, this is the amount of facilities costs allocated to this NPI from the parent organization. Organizations with only one NPI can omit this field or submit 0. Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., dollar-sign, comma) are not permitted.

Example values

8250.67

List records

To list records related to Facilities Costs, issue a GET request to the Facilities Cost endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

npiidintegeroptional

The Amber NPI identifier of the NPI whose data you want. If you omit the npiid, all NPIs' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/facilexp?org=1&year=2018&npiid=1" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":[
     {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_facil_name.1":"Main Facility"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_facil_ownership_type.1":"ownedmort"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_facil_square_feet.1":"1000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_facil_monthly_cost.1":"10000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_facil_shared_facil_pct_of_sqft_for_grd_amb.1":"100"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_facil_insurance":"2112"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_facil_maint":"3903"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_facil_utils":"4234"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_facil_taxes":"5512"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_facil_shared":"54300"
      }
   ]
}

Create or update records

To update Facility Cost records, issue a POST request to the Facility Cost endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org, npiid, and year, to specify the organization being updated, the NPI being updated, and the year of data being submitted. Beyond that, any combination of cost fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/facilexp -d '{"org":1,"year":2018,"npiid":1,"cost_facil_name.1":"Main Facility"}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"1 field(s) updated."}

Fields

Requests and responses for Vehicle Costs may contain one or more of the following fields:

Organization ID

Integer

org / orgid

Every organization in the system has a numeric ID. An organization may have one or more NPIs, each of which also have IDs. The Organization ID, though, is the single parent.

Example values

Year

Integer

year

Organization information may change year to year, so data also will be tagged with a four-digit year. This is the year covered by the submitted information (not the year in which it was entered).

Example values

NPI ID

Integer

npiid

This is the internal Amber identifier for an NPI. It is an integer, and is generally way fewer than 10-digits long (though it could be). This is NOT the CMS-assigned NPI identifier; it is specific to Amber.

Example values

Ambulance Name

String

cost_veh_amb_name.#

This is a user-defined string to help them keep track of which ambulance is which in the data. The # in the field name is an integer greater than or equal to 1, indicating the array number of the ambulance. The first ambulance entered will be 1, the next 2, and so on.

Example values (complete list)

Ambulance One

Galloping Gertie

Is Ambulance Owned or Leased?

String (fixed options)

cost_veh_owned_or_leased.#

This is whether the ambulance is owned or leased. The options are owned (Owned) or leased (Leased). The # in the field name is an integer greater than or equal to 1, indicating the array number of the ambulance. The first ambulance entered will be 1, the next 2, and so on.

Example values (complete list)

owned

leased

Is Ambulance Used to Transport Patients?

String (fixed options)

cost_veh_used_to_transport.#

This is whether the ambulance is used to transport patients. The options are yes (Used to Transport) or no (Not Used). The # in the field name is an integer greater than or equal to 1, indicating the array number of the ambulance. The first ambulance entered will be 1, the next 2, and so on.

Example values (complete list)

yes

no

Was Ambulance Donated?

String (fixed options)

cost_veh_donated.#

This is whether the ambulance was donated. The options are yes (Was Donated) or no (Was Not Donated). The # in the field name is an integer greater than or equal to 1, indicating the array number of the ambulance. The first ambulance entered will be 1, the next 2, and so on.

Example values (complete list)

yes

no

Ambulance Annual Depreciated Value

Number

cost_veh_amb_annual_deprec_val.#

For ambulances that are owned, the annual depreciated value of the ambulance. The # in the field name is an integer greater than or equal to 1, indicating the array number of the ambulance. The first ambulance entered will be 1, the next 2, and so on.

Example values

60792.20

Was Ambulance Remounted This Year?

String (fixed options)

cost_veh_remounted.#

For ambulances that are owned, whether or not the ambulance was remounted during the reporting period. The options are yes (Was Remounted) or no (Was Not Remounted). The # in the field name is an integer greater than or equal to 1, indicating the array number of the ambulance. The first ambulance entered will be 1, the next 2, and so on.

Example values (complete list)

yes

no

Ambulance Remount Cost

Number

cost_veh_remount_cost.#

For ambulances that were remounted during the year, the cost of the remount. The # in the field name is an integer greater than or equal to 1, indicating the array number of the ambulance. The first ambulance entered will be 1, the next 2, and so on.

Example values

32130.25

Ambulance Annual Lease Cost

Number

cost_veh_amb_lease.#

For ambulances that are leased, the annual cost of the lease. The # in the field name is an integer greater than or equal to 1, indicating the array number of the ambulance. The first ambulance entered will be 1, the next 2, and so on.

Example values

32130.25

Type of Non-Ambulance Vehicle

String (fixed options)

cost_veh_nonamb_type.#

This is type of the non-ambulance vehicle. The options are firetruck (Fire Truck), waterrescue (Water Rescue Vehicle), nontransporter (Responding Non-Transport), or other (Other Vehicle Type). The # in the field name is an integer greater than or equal to 1, indicating the array number of the non-ambulance vehicle. The first non-ambulance entered will be 1, the next 2, and so on.

Example values (complete list)

firetruck

waterrescue

nontransporter

other

Non-Ambulance Name

String

cost_veh_nonamb_name.#

This is a user-defined string to help them keep track of which non-ambulance is which in the data. The # in the field name is an integer greater than or equal to 1, indicating the array number of the ambulance. The first ambulance entered will be 1, the next 2, and so on.

Example values (complete list)

FlyCar One

Old Red

Is Non-Ambulance Owned or Leased?

String (fixed options)

cost_veh_nonamb_owned_or_leased.#

This is whether the non-ambulance is owned or leased. The options are owned (Owned) or leased (Leased). The # in the field name is an integer greater than or equal to 1, indicating the array number of the non-ambulance vehicle. The first non-ambulance entered will be 1, the next 2, and so on.

Example values (complete list)

owned

leased

Was Non-Ambulance Used for Ground Amb?

String (fixed options)

cost_veh_responded_or_supported.#

This is whether the non-ambulance was used to respond to ambulance calls or support ground ambulance operations. The options are yes (Was Used) or no (Was Not Used). The # in the field name is an integer greater than or equal to 1, indicating the array number of the non-ambulance vehicle. The first non-ambulance entered will be 1, the next 2, and so on.

Example values (complete list)

yes

no

Was Non-Ambulance Donated?

String (fixed options)

cost_veh_nonamb_donated.#

This is whether the non-ambulance was donated. The options are yes (Was Donated) or no (Was Not Donated). The # in the field name is an integer greater than or equal to 1, indicating the array number of the non-ambulance vehicle. The first non-ambulance entered will be 1, the next 2, and so on.

Example values (complete list)

yes

no

Non-Ambulance Annual Depreciated Value

Number

cost_veh_nonamb_annual_deprec_val.#

For non-ambulances that are owned, the annual depreciated value of the non-ambulance. The # in the field name is an integer greater than or equal to 1, indicating the array number of the non-ambulance vehicle. The first non-ambulance entered will be 1, the next 2, and so on.

Example values

60792.20

Non-Ambulance Annual Lease Cost

Number

cost_veh_nonamb_lease.#

For non-ambulances that are leased, the annual cost of the lease. The # in the field name is an integer greater than or equal to 1, indicating the array number of the ambulance. The first ambulance entered will be 1, the next 2, and so on.

Example values

32130.25

Non-Ambulance Percent of Mileage Attributed to Ground Ambulance Service

Number

cost_veh_nonamb_pct_to_grd.#

For non-ambulances, the percent of mileage for the year that is attributable to ground ambulance service. The # in the field name is an integer greater than or equal to 1, indicating the array number of the non-ambulance. The first non-ambulance entered will be 1, the next 2, and so on.

Example values

32130.25

Land Ambulance Mileage

Number

cost_veh_landamb_total_mileage

The total mileage of all land ambulances for this NPI for the year.

Example values

32130.25

Land Non-Ambulance Mileage

Number

cost_veh_landnonamb_total_mileage

The total mileage of all land non-ambulances for this NPI for the year.

Example values

32130.25

Water Ambulance Mileage

Number

cost_veh_wateramb_total_mileage

The total mileage of all water ambulances for this NPI for the year.

Example values

32130.25

Water Non-Ambulance Mileage

Number

cost_veh_waternonamb_total_mileage

The total mileage of all water non-ambulances for this NPI for the year.

Example values

32130.25

Vehicle Registration Costs

Number

cost_veh_reg

The total costs of vehicle registration for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted.

Example values

32130.25

Vehicle Licensing Costs

Number

cost_veh_license

The total costs of vehicle licensing for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted.

Example values

32130.25

Vehicle Insurance Costs

Number

cost_veh_insurance

The total costs of vehicle insurance for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted.

Example values

32130.25

Vehicle Maintenance Costs

Number

cost_veh_maint

The total costs of vehicle maintenance for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted.

Example values

32130.25

Percent of Maintenance Costs On Ground Ambulances

Number

cost_veh_ground_amb_pct_maint_cost

The percent of vehicle maintenance costs spent on ground ambulances for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted. Total of all maintenance cost percentages should be 100.0.

Example values

50.25

Percent of Maintenance Costs On Fire Trucks

Number

cost_veh_firetrucks_pct_maint_cost

The percent of vehicle maintenance costs spent on fire trucks for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted. Total of all maintenance cost percentages should be 100.0.

Example values

20.25

Percent of Maintenance Costs On Land Rescue Vehicles

Number

cost_veh_land_rescue_pct_maint_cost

The percent of vehicle maintenance costs spent on land rescue vehicles for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted. Total of all maintenance cost percentages should be 100.0.

Example values

20.25

Percent of Maintenance Costs On Water Rescue Vehicles

Number

cost_veh_water_rescue_pct_maint_cost

The percent of vehicle maintenance costs spent on water rescue vehicles for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted. Total of all maintenance cost percentages should be 100.0.

Example values

20.25

Percent of Maintenance Costs On Other Responding Non-Transport Vehicles

Number

cost_veh_other_respond_pct_maint_cost

The percent of vehicle maintenance costs spent on other responding non-transport vehicles for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted. Total of all maintenance cost percentages should be 100.0.

Example values

20.25

Percent of Maintenance Costs On Other Vehicles

Number

cost_veh_other_vehicles_pct_maint_cost

The percent of vehicle maintenance costs spent on other vehicles not included above for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted. Total of all maintenance cost percentages should be 100.0.

Example values

20.25

Vehicle Fuel Costs

Number

cost_veh_fuel

The total costs of vehicle fuel for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted.

Example values

32130.25

Percent of Fuel Costs On Ground Ambulances

Number

cost_veh_ground_amb_pct_fuel_cost

The percent of vehicle fuel costs spent on ground ambulances for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted. Total of all fuel cost percentages should be 100.0.

Example values

50.25

Percent of Fuel Costs On Fire Trucks

Number

cost_veh_firetrucks_pct_fuel_cost

The percent of vehicle fuel costs spent on fire trucks for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted. Total of all fuel cost percentages should be 100.0.

Example values

20.25

Percent of Fuel Costs On Land Rescue Vehicles

Number

cost_veh_land_rescue_pct_fuel_cost

The percent of vehicle fuel costs spent on land rescue vehicles for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted. Total of all fuel cost percentages should be 100.0.

Example values

20.25

Percent of Fuel Costs On Water Rescue Vehicles

Number

cost_veh_water_rescue_pct_fuel_cost

The percent of vehicle fuel costs spent on water rescue vehicles for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted. Total of all fuel cost percentages should be 100.0.

Example values

20.25

Percent of Fuel Costs On Other Responding Non-Transport Vehicles

Number

cost_veh_other_respond_pct_fuel_cost

The percent of vehicle fuel costs spent on other responding non-transport vehicles for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted. Total of all fuel cost percentages should be 100.0.

Example values

20.25

Percent of Fuel Costs On Other Vehicles

Number

cost_veh_other_vehicles_pct_fuel_cost

The percent of vehicle fuel costs spent on other vehicles not included above for this NPI for the year. Numerals from 0-9 and a decimal point are allowed. Other characters (e.g., commas or dollar-signs) are not permitted. Total of all fuel cost percentages should be 100.0.

Example values

20.25

Vehicle Costs Allocated From Parent

Number

cost_veh_other_shared

If an organization has multiple NPIs, this is the amount of other vehicle costs allocated to this NPI from the parent organization. Organizations with only one NPI can omit this field or submit 0. Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., dollar-sign, comma) are not permitted.

Example values

8250.67

List records

To list records related to Vehicle Costs, issue a GET request to the Vehicle Costs endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

npiidintegeroptional

The Amber NPI identifier of the NPI whose data you want. If you omit the npiid, all NPIs' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/vehicleexp?org=1&year=2018&npiid=1" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":[
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_owned_or_leased.1":"leased"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_used_to_transport.1":"yes"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_donated.1":"no"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_remounted.1":"no"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_amb_lease.1":"1200"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_nonamb_owned_or_leased.1":"leased"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_nonamb_type.1":"firetruck"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_responded_or_supported.1":"yes"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_nonamb_donated.1":"no"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_nonamb_lease.1":"1300"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_landamb_total_mileage":"500"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_landnonamb_total_mileage":"600"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_wateramb_total_mileage":""
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_waternonamb_total_mileage":""
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_reg":"150"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_license":"260"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_insurance":"370"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_maint":"480"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_ground_amb_pct_maint_cost":"50"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_firetrucks_pct_maint_cost":"15"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_land_rescue_pct_maint_cost":"25"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_water_rescue_pct_maint_cost":""
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_other_respond_pct_maint_cost":"8"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_other_vehicles_pct_maint_cost":"2"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_fuel":"20000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_ground_amb_pct_fuel_cost":"60"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_firetrucks_pct_fuel_cost":"10"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_land_rescue_pct_fuel_cost":"15"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_water_rescue_pct_fuel_cost":""
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_other_respond_pct_fuel_cost":"10"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_other_vehicles_pct_fuel_cost":"5"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_veh_other_shared":"10000"
      }
   ]
}

Create or update records

To update Vehicle Cost records, issue a POST request to the Vehicle Cost endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org, npiid, and year, to specify the organization being updated, the NPI being updated, and the year of data being submitted. Beyond that, any combination of cost fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/vehicleexp -d '{"org":1,"year":2018,"npiid":1,"cost_veh_ground_amb_pct_fuel_cost":91500}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"1 field(s) updated."}

Fields

Requests and responses for Equipment/Supply Costs may contain one or more of the following fields:

Organization ID

Integer

org / orgid

Every organization in the system has a numeric ID. An organization may have one or more NPIs, each of which also have IDs. The Organization ID, though, is the single parent.

Example values

Year

Integer

year

Organization information may change year to year, so data also will be tagged with a four-digit year. This is the year covered by the submitted information (not the year in which it was entered).

Example values

NPI ID

Integer

npiid

This is the internal Amber identifier for an NPI. It is an integer, and is generally way fewer than 10-digits long (though it could be). This is NOT the CMS-assigned NPI identifier; it is specific to Amber.

yeshave

yesdonthave

nohosp

nopaidbyother

nodonated

nomeds

Medication Costs

Number

cost_equip_meds

If the prior field (cost_equip_medication_has_cost) is yeshave, then this is the total cost for this NPI's medications. Numerals 0-9 and a decimal point are allowed. Other characters (e.g., comma, dollar-sign) are not permitted.

Example values

8215.15

Non-Medical Equip/Supply Costs Allocated From Parent

Number

cost_equip_nonmed_shared

If an organization has multiple NPIs, this is the amount of non-medical equipment and supply costs allocated to this NPI from the parent organization. Organizations with only one NPI can omit this field or submit 0. Only numerals 0-9 and a decimal point are allowed. Other characters (e.g., dollar-sign, comma) are not permitted.

Example values

8250.67

List records

To list records related to Other Revenue, issue a GET request to the Other Revenue endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

npiidintegeroptional

The Amber NPI identifier of the NPI whose data you want. If you omit the npiid, all NPIs' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/equipexp?org=1&year=2018&npiid=1" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":[
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_equip_capmedequip_cost_equip_deprec_cost":"1000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_equip_capmedequip_cost_equip_maint_cert_costs":"2000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_equip_capnonmedequip_cost_equip_deprec_cost":"2000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_equip_capnonmedequip_cost_equip_maint_cert_costs":"1000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_equip_noncapmedsupp_cost_equip_total_cost":"10000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_equip_uniforms_cost_equip_total_cost":"8000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_equip_noncapnonmedsupp_cost_equip_total_cost":"6000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_equip_medication_has_cost":"yeshave"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_equip_meds":"5000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_equip_nonmed_shared":"15000"
      }
   ]
}

Create or update records

To update Equipment/Supply Cost records, issue a POST request to the Equipment/Supply Cost endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org, npiid, and year, to specify the organization being updated, the NPI being updated, and the year of data being submitted. Beyond that, any combination of cost fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/equipexp -d '{"org":1,"year":2018,"npiid":1,"cost_equip_nonmed_shared":17500}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"1 field(s) updated."}

Fields

Requests and responses for Other Costs may contain one or more of the following fields:

Organization ID

Integer

org / orgid

Every organization in the system has a numeric ID. An organization may have one or more NPIs, each of which also have IDs. The Organization ID, though, is the single parent.

Example values

Year

Integer

year

Organization information may change year to year, so data also will be tagged with a four-digit year. This is the year covered by the submitted information (not the year in which it was entered).

Example values

NPI ID

Integer

npiid

This is the internal Amber identifier for an NPI. It is an integer, and is generally way fewer than 10-digits long (though it could be). This is NOT the CMS-assigned NPI identifier; it is specific to Amber.

8250.67

List records

To list records related to Facilities Costs, issue a GET request to the Facilities Cost endpoint.

Returned records do not include fields where a user has not ever entered information.

You can use the following parameters to filter the results:

orgintegerrequired

The ID of the organization whose records you are seeking. This is a required field, and the API key you are using must have access to that organization's information.

yearintegeroptional

The year of the data you want. If you omit the year, all years' data will be returned.

npiidintegeroptional

The Amber NPI identifier of the NPI whose data you want. If you omit the npiid, all NPIs' data will be returned.

Example Request

$ curl "https://emsamber.com/apiv1/otherexp?org=1&year=2018&npiid=1" -H "Accept: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{
   "data":[
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_med_dir_k_direct":"100"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_billing_k_direct":"200"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_accounting_k_direct":"300"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_vehicle_svc_k_direct":"400"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_dispatch_svc_k_direct":"500"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_facil_maint_svc_k_direct":"600"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_it_support_k_direct":"700"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_software_direct":"800"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_board_costs_direct":"900"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_other_prof_fees_direct":"800"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_advertising_direct":"700"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_events_meetings_direct":"600"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_physicals_recruiting_direct":"500"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_training_direct":"400"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_non_travel_training_direct":"300"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_laundry_direct":"200"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_waste_removal_fees_direct":"100"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_oversight_doc_fees_direct":"200"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_911svc_direct":"300"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_tollroads_direct":"400"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_req_localfees_direct":"500"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_compliance_fees_direct":"600"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_bizreg_fees_direct":"700"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_k_svc_shared":"15000"
      },
      {  
         "orgid":1,
         "year":2018,
         "npiid":1,
         "cost_other_misc_shared":"16000"
      }
   ]
}

Create or update records

To update Other Cost records, issue a POST request to the Other Cost endpoint.

All creation and updating of records is non-destructive: attributes not specifically created or updated will be left unaffected.

Your request must contain parameters org, npiid, and year, to specify the organization being updated, the NPI being updated, and the year of data being submitted. Beyond that, any combination of cost fields is allowed.

The response will be a JSON object with key of either "success" or "error", along with a description.

Example Request

$ curl https://emsamber.com/apiv1/otherexp -d '{"org":1,"year":2018,"npiid":1,"cost_other_tollroads_direct":6199}' -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY"

Example Response

{"success":"1 field(s) updated."}

Introduction

Authentication

Example Using Bearer Token

Organization Info

Fields

Field Name

Type

Description

Example values

Example values

Example values

Example values

Example values

Example values

Example values

Example values

Example values

Example values

Example values

Example values

Example values

Example values

Example values

Example values

Example values

Example values

Example values

Example values

List records

Example Request

Example Response

Create or update records

Example Request

Example Response

NPIs

Fields

Field Name

Type

Description

Example values

Example values

Example values

Example values

Example values (complete list)

Example values

List records

Example Request

Example Response

Create or update records

Example Request

Example Response

NPI Contacts

Fields

Field Name

Type

Description

Example values

Example values

Example values

Example values

Example values

Example values

Example values

Example values

Example values

List records

Example Request

Example Response

Create or update records

Example Request

Example Response

NPI Profile

Fields

Field Name

Type

Description

Example values

Example values

Example values

Example values