International Patient Access - Local Development build (v1.0.0-preview). See the Directory of published versions
Raw OpenAPI-Swagger Definition file | Download
http://hl7.org/fhir/uv/ipa/CapabilityStatement/ipa-serverInternationalPatientAccessAPIjson, SHOULD support xmlapplication/json-patch+jsonThis section describes the basic rules for the International Patient Access server actor that is responsible for providing responses to queries submitted by International Patient Access requestors. The complete list of FHIR profiles, RESTful operations, and search parameters supported by International Patient Access servers are defined in this CapabilityStatement. International Patient Access clients have the option of choosing from this list to access necessary data based on their local use cases and other contextual requirements.
serverThe IPA Server SHALL:
The IPA Server SHOULD:
meta.profile attribute for each instance.
- See the General Security Considerations section for requirements and recommendations.
- A server SHALL reject any unauthorized requests by returning an
HTTP 401unauthorized response code.
transaction interaction.batch interaction.search-system interaction.history-system interaction.The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include_revinclude| Resource Type | Profile | R | S | U | C | Searches | _include | _revinclude | Operations |
|---|---|---|---|---|---|---|---|---|---|
| AllergyIntolerance | http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-allergyintolerance | y | y | patient, patient+clinical-status | Provenance:target | ||||
| Condition | http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-condition | y | y | patient, patient+clinical-status, patient+category, patient+category+clinical-status, patient+code, patient+onset-date | Provenance:target | ||||
| DocumentReference | http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-documentreference | y | y | _id, patient, patient+category, patient+category+date, patient+type, patient+contenttype, patient+status, patient+type+date, patient+type+period | Provenance:target | $docref | |||
| Immunization | http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-immunization | y | y | patient, patient+date, patient+status | Provenance:target | ||||
| Medication | http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-medication | y | Provenance:target | ||||||
| MedicationRequest | http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-medicationrequest | y | y | category, code, patient, patient+intent, patient+intent+authoredon, patient+intent+status | MedicationRequest:medication | Provenance:target | |||
| MedicationStatement | http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-medicationstatement | y | y | subject, subject+status | MedicationRequest:medication | Provenance:target | |||
| Observation | http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-observation Additional supported profiles: http://hl7.org/fhir/StructureDefinition/vitalsigns | y | y | patient, patient+category, patient+code, patient+category+date, patient+category+status, patient+code+date | Provenance:target | ||||
| Patient | http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-patient | y | y | _id, birthdate, family, gender, given, identifier, name, family+gender, birthdate+family, birthdate+name, gender+name | Provenance:target | ||||
| Practitioner | http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-practitioner | y | Provenance:target | ||||||
| PractitionerRole | http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-practitionerrole | y | PractitionerRole:endpoint, PractitionerRole:practitioner | Provenance:target |
resolveshttp://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-allergyintolerance
read, search-type.| Conformance | Parameter | Type |
|---|---|---|
| SHALL | patient | reference |
| Conformance | Parameters | Types |
|---|---|---|
| SHOULD | patient+clinical-status | reference+token |
referenceThe client SHALL provide at least a id value and MAY provide both the Type and id values.
The server SHALL support both.
tokenactive | inactive | resolved
resolveshttp://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-condition
read, search-type.| Conformance | Parameter | Type |
|---|---|---|
| SHALL | patient | reference |
| Conformance | Parameters | Types |
|---|---|---|
| SHOULD | patient+clinical-status | reference+token |
| SHOULD | patient+category | reference+token |
| SHOULD | patient+category+clinical-status | reference+token+token |
| SHOULD | patient+code | reference+token |
| SHOULD | patient+onset-date | reference+date |
tokenCode for the condition
referenceThe client SHALL provide at least a id value and MAY provide both the Type and id values.
The server SHALL support both.
tokenThe clinical status of the condition
tokenThe category of the condition
dateDate of onset for the condition
resolveshttp://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-documentreference
read, search-type.| Conformance | Parameters | Types |
|---|---|---|
| SHALL | patient+category | reference+token |
| SHALL | patient+category+date | reference+token+date |
| SHALL | patient+type | reference+token |
| SHOULD | patient+contenttype | reference+token |
| SHOULD | patient+status | reference+token |
| SHOULD | patient+type+date | reference+token+date |
| SHOULD | patient+type+period | reference+token+date |
dateWhen this document reference was created
dateTime of service that is being documented
referenceThe client SHALL provide at least an id value and MAY provide both the Type and id values.
The server SHALL support both.
tokenCategorization of document
tokenKind of document (LOINC if possible)
tokenMime type of the content, may include charset
tokencurrent | superseded | entered-in-error
resolveshttp://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-immunization
read, search-type.| Conformance | Parameter | Type |
|---|---|---|
| SHALL | patient | reference |
dateVaccination (non)-Administration Date
referenceThe client SHALL provide at least an id value and MAY provide both the Type and id values.
The server SHALL support both.
tokenImmunization event status
resolvesThe MedicationStatement and MedicationRequest resources can represent a medication, using an external reference to a Medication resource. If an external Medication Resource is used in a MedicationStatement or a MedicationRequest, then the READ and SEARCH Criteria SHALL be supported.
http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-medication
read.resolveshttp://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-medicationrequest
read, search-type.tokenReturn prescriptions of this medication code
dateReturns prescriptions written on this date
referenceThe client SHALL provide at least an id value and MAY provide both the Type and id values.
The server SHALL support both.
tokenReturns prescriptions with different categories
tokenReturn prescriptions with this encounter identifier
tokenStatus of the prescription
resolvesThe MedicationStatement resources can represent a medication using either a code or refer to the Medication resource. When referencing Medication, the resource may be contained or an external resource. The server application MAY choose any one way or more than one method, but if an external reference to Medication is used, the server SHALL support the _include` parameter for searching this element. The client application must support all methods.
For example, A server SHALL be capable of returning all medications for a patient using one of or both:
GET /MedicationRequest?patient=[id]
GET /MedicationRequest?patient=[id]&_include=MedicationRequest:medication
http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-medicationstatement
read, search-type.| Conformance | Parameter | Type |
|---|---|---|
| SHALL | subject | reference |
referenceReturn statements that match the given status
tokenReturn statements that match the given status
resolveshttp://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-observation
read, search-type.| Conformance | Parameter | Type |
|---|---|---|
| SHALL | patient | reference |
dateObtained date/time. If the obtained element is a period, a date that falls in the period
tokenThe code of the observation type
referenceThe client SHALL provide at least an id value and MAY provide both the Type and id values.
The server SHALL support both.
tokenThe classification of the type of observation
tokenThe status of the observation
resolvesread, search-type.tokenThe client SHALL provide both the system and code values.
The server SHALL NOT support only code values.
dateA client SHALL provide a value precise to the day.
A server SHALL support a value a value precise to the day.
tokenThe client SHALL provide at least a code value and MAY provide both the system and code values.
The server SHALL support both.
stringA server SHALL support a value precise to the day.
resolveshttp://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-practitioner
read.resolveshttp://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-practitionerrole
read.