Product

IMAT Solutions V8

Capability and Costs of Certified IMAT Version 8

Description of Capability:

 Load, parse, and store inbound clinical documents (e.g., C-CDA, QRDA I, HL7 v2, FHIR)

 Calculate eCQMs the user chooses

 Export QRDA III documents

Costs or Fees

 Software is licensed based on yearly fee, license fees is volume-based as determined by provider volumes and includes support as well as maintenance, hosting, and upgrades. A one-time implementation fee based on the number of modules licensed is charged. There is no limit on users or outbound data.

ONC Disclaimer: “This Health IT Module is 2015 Cures Edition compliant and has been certified by an ONC-ACB in accordance with the applicable certification criteria adopted by the Secretary of Health and Human Services. This certification does not represent an endorsement by the U.S. Department of Health and Human Services.”

Electronic Health Information Export

IMAT contains a CCD on-demand product which uses all information about a patient across multiple source records. There are three methods of access available to users who have access to PHI, and have been given a role to access the CCD on-demand product.

UI – IMAT has a UI that allows users to specify an MPI, date range to filter results to, MRN, and a filter to exclude and include facilities. This can be accessed from a UI located at https://{customerurl}/brand/ccda.html.

RESTful API – IMAT has a RESTful API which allows exporting of a single patient or can be used to export a population.

Interface engine – Using IMAT’s interface engine, you can generate and send CCDs through standard IHE profiles.

To gain access to the API an access token must be generated. IMAT recommends this access token be limited to the APIs required for export; this is the /extensions/IMAT-API and /search/results paths. For patient populations, you will need to use /search instead of /search/results. Access tokens should be limited to an IP or IP range where possible.

Single Patient Export

The Generate CCD call is an asynchronous command, this means that the system will return an ID used for tracking status and retrieving items. The following three API calls will be used for the entire lifecycle of the call.

GET: /extensions/IMAT-API/patient/{MPID}/generate-ccd-script

This starts the ASYNC process within the IMAT platform. IMAT will start generating the CCD in the background and status can be retrieved using the status call.

Request example:

The response from this call will be an ID used for tracking status and retrieving the generated CCD.

Example Response:

mpid={number} – This is the internal IMAT MPID for the patient (a patient lookup call may be issued to lookup the MPID if not known)

start_date,end_date={date yyyymmdd} – Used to filter the data included in the CCD to the date range supplied. If no dates are passed then the CCD will use all data for a patient within IMAT

facility={string} – A comma separated list used to filter the CCD to only include data from a particular facility

exclude_facility={string} – A comma separated list used to ignore data from included facilities

fmrn={string} – A facility medical record number of the format of facility~mrn where facility can be the name or OID of the location. This can be used to filter records that include this MRN from this facility.

GET: /search/results/{result_id}/status

This retrieves the status of the CCD on demand process. This will return one of the following statuses:

Running – The request is still processing
Aborted – The patient doesn’t have enough information to process a CCD
Failed – IMAT has run into a problem generating the CCD
Complete – A user may now retrieve the completed CCD

Request example:

Example Response:

GET: /search/results/{result_id}/output/{filename}

The call retrieves output from the CCD generation process. The CCD file is named ccda.xml.

Request example:

Example Response:

Patient Population Export

A user will be set up with access granted to the patient population which is being requested. This can come from a treatment relationship, member roster, or some other data driven criteria. The user will then issue a call to get a list of all MPIDs available for export using the following command.

GET: /search

Request example:

q={string} – IMAT Query string to search the data. ()UNIVERSE is a keyword for all data.
fields={string} – The fields that are being requested back.
store={string} – Limits the search to the specified store.
format={string} – Available formats are CSV or XML.

The example searches for all patients available to the users, and extracts a list of MPIs in either XML or CSV targeting the MPI store.

Example response for CSV:

Example response for XML:

<response xmlns:ps="http://software.perfectsearchcorp.com/sdk/query-v1">
	<timestamp>2023-12-04 11:30:22</timestamp>
	<hits total="-1" sample="0" skip="0" count="10" match="exact" grosscount="10">
		<hit ref="2" score="0" store="1101" space="1101">
			<mpid>2</mpid>
		</hit>
		<hit ref="3" score="0" store="1101" space="1101">
			<mpid>3</mpid>
		</hit>
		<hit ref="22" score="0" store="1101" space="1101">
			<mpid>11</mpid>
		</hit>
		<hit ref="26" score="0" store="1101" space="1101">
			<mpid>15</mpid>
		</hit>
		<hit ref="27" score="0" store="1101" space="1101">
			<mpid>16</mpid>
		</hit>
		<hit ref="30" score="0" store="1101" space="1101">
			<mpid>19</mpid>
		</hit>
		<hit ref="32" score="0" store="1101" space="1101">
			<mpid>21</mpid>
		</hit>
		<hit ref="34" score="0" store="1101" space="1101">
			<mpid>23</mpid>
		</hit>
		<hit ref="35" score="0" store="1101" space="1101">
			<mpid>24</mpid>
		</hit>
		<hit ref="38" score="0" store="1101" space="1101">
			<mpid>27</mpid>
		</hit>
	</hits>
	<query lang="eng">
		<q> ()UNIVERSE </q>
	</query>
	<timing>
		<prep_sec>0.000067</prep_sec>
		<search>
			<engine_sec>0.000005</engine_sec>
				<total_search_sec>0.000131</total_search_sec>
		</search>
		<build_report_sec>0.026357</build_report_sec>
		<total_sec>0.026555</total_sec>
	</timing>
</response>

For each MPID returned, use the APIs for single patient export.

IMAT also has an interface engine which can be used to programmatically export patients.

IMAT’s professional services team may also be contacted to help with or complete any of these tasks on a time and materials basis.

IMAT’s Signed Server JWK Set

{
  "keys" : [
     {
       "kty" : "RSA",
       "use" : "sig",
       "kid" : "uY3D3pgchDVqW_E24XAEcrSFKOibZiq--T8rplxv8fg",
       "e"   : "AQAB",
       "n"   : "ryxpVMmX87F4D5Ir9OPa4DiMj9uHYSAUhpC48im1RbehCnAwENjIWfQCqrGVO2YqQBGd5FgrxZ-TLPyp

GDC0ir0YFGRl6YvSRy7N0vWE4HbpQ88yp0nhaVDonPpruXOeATEU-wdNuE1zxW1US-NE38_Nb0WjZ3L-1vKKhzY-l9Z4sz2R

epdFs4zxtsiyj5Aoq-Rih3LfIslHYLMn9W5R8tOcNA73O-9LAY1cDHhyOZ-huq9NA4yUaMebOWU_gQFoCglG40mYTkVr_-gY

mYmwHib2sEKjhSjNhtwXb9alKtXD8mgFP8LS4KRUN4yzyyf8G04t0NOgnu7eb5AGrrx1UQ"
     }
  ]
}

For more information see IMAT’s API documentation page for more detailed instructions. A specific version can be found at https://{base_url}/ui/documentation/#/ or a more generic version can be found at https://docs.imat.io.

IMAT’s CCD conform to the latest CDA R2.1 R4.1 STU 2023 specifications