Configuration
      Back to home
      1. AngelTrack Knowledge Base
      2. General Topics
      3. Configuration

      Document Templates / Signature Forms

      A walkthrough of how AngelTrack's templates work for each type of document and signature, how you can customize them.

      There are many places in AngelTrack where blocks of legal text appear. These text blocks are called "Document Templates", and you can edit their content.

      On the Settings page, the Document Templates item lists all templates available for editing. Their filenames are self-explanatory. Click a filename to bring up the editor to view the content and make changes.

      Some Document Templates are for PCR Signature Verbiage

      Some of the document templates are used for the verbiage blocks on the various PCR signature forms. You can freely customize the content to match your requirements.

      The templates are versioned, so your changes will take effect for all signatures going forward, but will not alter the verbiage on signature forms already collected.

      For any document template which is a PCR signature form, you will also see a set of NEMSIS value checkboxes that indicate the signature form's purpose. These values are used when AngelTrack reports the signature form to your state trauma registry, so that downstream users of the data can understand what the signature represents.

      Built-in Verbiage

      Your AngelTrack cloud server has pre-installed text for each document template, including the fourteen basic PCR signature forms.

      These pre-installed texts are not a substitute for legal documents nor are they legal advice. They are starter texts. Your legal team must review the texts, so as to verify they are consistent with the particular state and local regulations that apply to your operation, and also meet your own documentation standards.

      Built-in Spanish translations

      Some of the document templates have Spanish translations included. This content has been professionally translated to Latin-American Spanish by a native speaker. The translation is included in the template text, at the bottom, under the English version.

      If you decide to modify the English text, then you must commission your own re-translation to Spanish. We recommend against using computer translation for legal documents.

      Custom PCR Signature Forms

      Your AngelTrack server comes with two customizable PCR signature forms:

      • UserConfigurableOtherSignature1
      • UserConfigurableOtherSignature2

       If you input any verbiage text into those templates, then they will appear in the PCR for use by your crews. AngelTrack does not enforce any requirements for the collection of these two signature forms; they will be optional for the crews.

      If you activate the Enterprise PCR add-on license, then you can add new signature forms to the PCR. Your new forms can "act like" any of the base forms, for example you could add a hardship form that "acts like" the "Payment Authorization" form and thus will satisfy AngelTrack's business logic for that signature requirement.

      To learn more about the Enterprise PCR license and its many features, please visit the Enterprise PCR Guide.

      Adding a New PCR Signature Form

      To add a new signature form to the PCR (NEMSIS + NFIRS), do the following:

      1. Login to AngelTrack with Administrator or Captain privileges.
      2. Navigate to the Settings page, and click the Document Templates item.
      3. Review the current forms to make sure the form you want hasn't already been created and perhaps is now inactive.
      4. Click the plus sign Add-Sep-21-2022-08-52-48-77-PM to add a new form. (If you don't already have your Enterprise PCR add-on license activated, you will be taken to the Feature Buffet page to activate it.)
      5. The "Add New Document Page" will open.
      6. In the "Template content" box, paste the legal verbiage that is to appear at the top of the signature form. Be sure to include a translation for whatever is the secondary language spoken in your service area. You can scroll down to see what helper variables you can also embed in the content.
      7. In the "Form name" box, type a description that tells the crew members the purpose of the form.
      8. For the "Acts like" option, if your form will suffice in lieu of one of the standard required forms, make that selection; otherwise, leave it set to "None".
      9. For the "NEMSIS reports as", select all that apply. These options will communicate to the EMS trauma registry what is signified by the signed form. The built-in list contains the standard NEMSIS values, but you can add new choices via AngelTrack's custom picklist values system, if any downstream consumer of your data (such as your billing system) needs to specifically identify a signature type.
      10. When you click "Save", the form will immediately appear in the PCR. 

      If you change your mind later, you can deactivate your signature form, without affecting any existing signatures that were collected against it.

      Deactivating Signature Forms

      You can deactivate signature forms that your crews do not or should not use. And you can change your mind later and reactivate them.

      But be careful: Make sure that there is always at least one form available for each requirement in AngelTrack's signature-requirements business logic:

      • Payment auth (at least one of the three types)
      • Receiving facility (at lease one of the two types)
      • Refusal of treatment
      • AMA
      • ABN
      • Narcotics used
      • Narcotics wasted
      • Authoring crew member attestation

      Embedded Variables

      The text of a template can contain variables, which AngelTrack automatically fills-in with live data. Variables work the same in both the English and Spanish texts.

      You may use as many of the following variables as you wish, wherever in the text you wish:

      Variable Automatically Replaced With
      [BUSINESS_NAME] The full name of the business, as configured in the .
      [BUSINESS_DISPATCHTELEPHONE] The dispatch telephone number (or main number) for the business, as configured in the Business Information page.
      [BUSINESS_STATE] The official abbreviated name of the business home state, as configured in the Business Information page.
      [BUSINESS_STATE_LICENSE_NUMBER] The state license number of the business, as configured in the Business Information page.
      [BUSINESS_STATE_AGENCY_NUMBER] The state agency number of the business, as configured in the Business Information page.
      [BUSINESS_NPI] The business National Provider Identifier number, as configured in the Billing Configuration page.
      [BUSINESS_TAXID] The federal tax ID (aka EIN) number, as configured in the Business Information page.
      [BUSINESS_WEBSITE] The URL of the website of the billing contact, as configured in the Business Information page.
      [BUSINESS_SLOGAN] The business slogan, as configured in the Business Information page.
      [BUSINESS_BILLINGNAME] The name of the business per its NPI paperwork, as configured in the Billing Configuration page.
      [BUSINESS_BILLINGADDRESS1] The first line of the street address of the billing contact, as configured in the Billing Configuration page.
      [BUSINESS_BILLINGADDRESS2] The second line of the street address of the billing contact, as configured in the Billing Configuration page.
      [BUSINESS_BILLINGCITY] The city portion of the billing contact's address, as configured in the Billing Configuration page.
      [BUSINESS_BILLINGSTATE] The state portion of the billing contact's address, as configured in the Billing Configuration page.
      [BUSINESS_BILLINGZIP] The ZIP code of the billing contact's address, as configured in the Billing Configuration page.
      [BUSINESS_BILLINGTELEPHONE] The voice telephone number of the billing contact, as configured in the Billing Configuration page.
      [BUSINESS_BILLINGFAX] The fax telephone number of the billing contact, as configured in the Billing Configuration page.
      [BUSINESS_BILLINGEMAIL] The email address of the contact person at the billing office, be it in-house or outsourced, as configured in the Billing Configuration page.

      For example, the following text in a Document Template:

      The undersigned agrees to remit to [BUSINESS_NAME] all necessary information to process . . .

      ...automatically becomes this:

      The undersigned agrees to remit to Acme EMS all necessary information to process . . .

      You may place any number of variables at any places within the Document Template's text, and whenever the text is displayed to a user, AngelTrack will resolve all variables to their underlying data.

      The PCR Narrative AutoComposer Uses a Template Too

      The AutoCompose feature in the PCR is driven by a document template, named PCRNarrative.

      By default, the template contains just this:

      [AUTOCOMPOSE_ENROUTE]

      [AUTOCOMPOSE_ONSCENE]

      [AUTOCOMPOSE_TRANSPORTING]

      [AUTOCOMPOSE_SYMPTOMSANDIMPRESSIONS]

      [AUTOCOMPOSE_DESTINATION]

      EOR

      Each of those variables represents one of the five sections of a standard chronological narrative. AutoCompose will generate those sections and arrange them in the narrative according to the positions of the variables in the template. Likewise you can remove one, two, three, four, or all five of those variables if you do not wish to allow AutoCompose to write that section. In other words, you can remove a variable from the template if you require the crew to write that section from scratch, without software assistance.

      You can also add static text, as well as AngelTrack document template variables, if you wish to include extra standard elements in the narrative.