Connectathon 2026 Wiki

Racsel logo
Back to home

Tasks · T1.2-A

Register patient IPS

View flow

Query the MPI, resolve terminology, build the IPS, and persist it in country A's national node using ITI-65.

Requirements

Pre Track enablement complete

Links

Expected response

The patient is retrieved from MPI, the IPS transaction/document Bundles are built with required clinical resources, local terminology is translated, and the IPS is persisted.

Evidence

HTTP response JSON showing created resources.

Observations

Test case: TK1.2_TC04. The presencial Connectathon stage may route requests through the Gazelle proxy.

Requests to run

Collection

PDQm - Qualification PDQm ITI-78

Query Patient with identifier

curl -X GET "https://gazelle.racsel.org/pdqm-fhir-simulator/IHE/fhir/Patient?identifier=BRZ9007" \
  -H "Accept: application/fhir+json"

Expected response

HTTP 200 OK with a Bundle of Patient resources used to build the IPS.

Collection

Terminology server - FHIR terminology

ITI-98 and ITI-101 terminology checks

curl -X GET "${TERMINOLOGY_SERVER}/CodeSystem/\$lookup?system=${LOCAL_CODESYSTEM_VACUNAS}&code=L30" \
  -H "Accept: application/fhir+json"

curl -X GET "${TERMINOLOGY_SERVER}/ConceptMap/\$translate?code=L30&system=${LOCAL_CODESYSTEM_VACUNAS}&targetsystem=${SNOMED_CODESYSTEM}" \
  -H "Accept: application/fhir+json"

Expected response

HTTP 200 responses showing local code lookup and translation to the terminology required by the IPS guide.

Collection

National Node - LACPass IPS

ITI-65 Provide Document

curl -X POST "${COUNTRY_A_NODE}/fhir" \
  -H "Content-Type: application/fhir+json" \
  -H "Accept: application/fhir+json" \
  --data-binary @ips-transaction-bundle.json

Expected response

HTTP 200 or 201 with JSON indicating the IPS transaction resources were created.