A discussion about each API endpoint can be found at API walk-through

How to administer a stateless assessment Stateless Assessment

How to customize a stateless assessment Stateless Customization

New Stopping Rules for Selected PROMIS CATs New Stopping Rules

How to localize a form in the API Localize Forms

Form(s) endpoint and LOINC coding.

Verify/Turn on the Windows features that are displayed below.

Create an Application Pool for the API application.

Add an ASP.NET application to the website and assign the pool to the app. *Note the application needs to be below the root website

Verify the database Server authentication supports both SQL Server and Windows Authentication mode

When I navigate to my api instance I get the following error:

When I navigate to my api instance I get the following error:

If you are upgrading and are more than one release behind the current version, then the quickest way to upgrade is:

1.) Restore the provided database (\db\IRT_API_DISTR.bak) on the same server with a different name. You could modify the restore_db.sql script to accomplish this.

2.) Add the current sql user to the new database and add it to the API_Users role. This is similar to the provided db_User.sql without the first command that creates the user on the server. You will need to update the USE statement for the correct db name.

3.) Move over the dbo.Registration record(s) to the new database.

4.) Update the web.config for the new database.

If you are using statefull endponts (i.e. Assessments, Participants) then you will also have to move the data in the dbo.State and dbo.Results tables.

Follow the instructions in the README for the website, basically copy and paste (make sure not to foget to update the web.config)

Do you have population based norms for T-Scores?

A lookup table for selected norms is included in /docs/TScore_Percentile.xlsx.
Percentiles are included based on gender and age groups.

Administering Illness Impact measures are different than other measures because 3 items are presented for each request

Illness Impact measures are archived, but they still can be administered, by using the FormOID listed below:

Syntax of Illness Impact measures

You will need to present three items on the screen. The first item will be the stem and will NOT have mappings associated with it. Do not respond to this item. The next two items (i.e. 'before' and 'since' items will have itemID followed by .b .a) will have mappings and these are the two items that you will respond to.

Submitting data for Illness Impact measures

FormItemOID attributes must be posted along with ItemResponseOID and Response. Each form-data variable is piped.

An example of POSTed form-data variables is below

Below is what a trace request would look like

POST /ac_api/2014-01/Participants/c720c55b-ad45-4481-a2db-5bee9db475ce.json HTTP/1.1
Host: localhost
Authorization: Basic MzlD ... A==
Cache-Control: no-cache

----WebKitFormBoundaryE19zNvXGzXaLvS5C

Content-Disposition: form-data; name="FormItemOID"

B5E5F9BD-2915-4274-AD3E-9CFC2861B6EE|6F1440CB-20F2-457B-A7F5-8C41CDD69175
----WebKitFormBoundaryE19zNvXGzXaLvS5C
Content-Disposition: form-data; name="ItemResponseOID"

48E3B064-CA1E-4936-A96D-0A763392E3D6|14DD8FC6-0E01-4620-863E-D1F7672D22F4
----WebKitFormBoundaryE19zNvXGzXaLvS5C
Content-Disposition: form-data; name="Response"

3|3
----WebKitFormBoundaryE19zNvXGzXaLvS5C