Mobile Patient Identity Feed (IHE ITI-104)


1 Background

Current implementation is based on IHE PIXm v3.0.4 (trial implementation of IHE PIXm) which is based in FHIR R4. This is an initial implementation of API-service providing option to register patient in NHN PIX-service.

term PIX ⇒ Patient Identifier Cross-referencing

This service is a RESTful implementation of IHE ITI-44 message "Patient Identity Feed HL7 V3" (https://profiles.ihe.net/ITI/TF/Volume2/ITI-44.html)

2 API-scope

There is currently no prerequisity for usage of API-scope to use this service. Might be subject to change in future

3 Endpoint

PUT https://api.pjd.test.nhn.no/R4/fhir/Patient

4 Messages

Messages follow IHE-spesification as described on https://profiles.ihe.net/ITI/PIXm/ITI-104.html

Service is currently supporting just "registering" new patients.

Removing, resolving duplicates or revising existing records is not supported yet

4.1 Message request

Adding patient record example

PUT http://api.pjd.test.nhn.no/fhir/Patient HTTP/1.1
Accept: application/fhir+json
Content-Type: application/fhir+json

{
  "resourceType" : "Patient",
  "identifier" : [
    {
      "system" : "urn:oid:2.16.578.1.12.4.1.1",
      "value" : "21037115874"
    }
  ],
  "active" : true,
  "name" : [
    {
      "family" : "OST",
      "given" : [
        "SPISS"
      ]
    }
  ],
  "gender" : "female",
  "birthDate" : "1958-01-30"
}

4.2 Message response

If successful [HTTP-200] than message response contains list of known assigning authorities for spesified patient.

HTTP Status Description
HTTP-201 Ok Successfully processed and response follows
HTTP-400 Bad Request Something was not registered properly
HTTP-404 Not Found Patient not found
HTTP-401 Unauthorized There is something wrong with JWT-token
HTTP-500 Internal server error Something technical went really wrong here [token exchange, internal XDS communication etc.]

5 Validation of existing messages

Norsk helsenett used IHE Gazelle Validation tool under development of our services and messages has been validated by using following tool: https://gazelle.ihe.net/evs/home.seam