Get a list of historical versions by allergy ID
get
/20240101/allergies/{allergyId}/versions
Retrieves the historical versions for the allergy ID. Each history contains the changes from the previous version.
Request
Path Parameters
-
allergyId(required): string
The unique identifier of the allergy.
Query Parameters
-
limit: integer
Minimum Value:
100Maximum Value:100For list pagination. The maximum number of results per page, or items to return in a paginatedListcall.Default Value:100 -
page: string
Minimum Length:
1For list pagination. The value of the opc-next-page response header from the previous List request. -
patientId(required): string
The patient ID to filter the resource query against.
Header Parameters
-
accept: string
Specifies which media types are acceptable for the response. Defaults to
application/json.Default Value:application/json -
accept-charset: string
Specifies which character sets are acceptable for the response. Defaults to
UTF-8.Default Value:UTF-8 -
authorization(required): string
Contains the credentials to authenticate a consumer to the service.
-
opc-request-id: string
Unique Oracle Health assigned identifier for the request. If you need to contact Oracle about a particular request, provide the request ID. The only valid characters for request IDs are letters, numbers, underscore, and dash.
Response
Supported Media Types
- application/json
200 Response
Success.
Headers
-
opc-next-page: string
For list pagination. When this header appears in the response, additional pages of results remain.
-
opc-prev-page: string
For list pagination. When this header appears in the response, additional pages of results remain.
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : AllergyVersionCollection
Type:
objectThe list of all the versions for an allergy.
Show Source
-
items(required):
array items
Unique Items Required:
trueThe list of allergy versions for an allergy.
Nested Schema : items
Type:
arrayUnique Items Required:
trueThe list of allergy versions for an allergy.
Show Source
-
Array of:
object AllergyVersionSummary
A version of an allergy that includes
AllergySummaryand other fields that display changes from the previous version.
Nested Schema : AllergyVersionSummary
Type:
objectA version of an allergy that includes
Show Source
AllergySummary and other fields that display changes from the previous version.-
allergyFieldUpdates:
array allergyFieldUpdates
The list of changes made to allergy fields in the current instance. This value can be null.
-
allergySummary(required):
object AllergySummary
The summary of an allergy that contains only important information about the allergy.
-
areNotesAdded(required):
boolean
Boolean flag to indicate if notes were added to the current instance.
-
combineDetails:
object Combine
The details of where the changes to an allergy based on a combine came from.
-
effectiveDateTimePeriod(required):
object DateTimePeriodWithoutZone
A representation of a date and time range without time zone information.
-
lastModifiedBy(required):
object PersonSimple
A simple representation of the individual person that was retrieved. The individual could be a personnel member (provider), a patient, or a nonpatient person.
-
lastModifiedDateTime(required):
string(date-time)
The date and time that represents the end of the current instance's effectiveness in the ISO-8601 representation of the date and time format (YYYY-MM-DDTHH:MM:SS:SSSZ) as defined by RFC 3339.Example:
2018-06-16T21:31:35.457Z -
reactionVersions:
array reactionVersions
The versions of reactions associated with the current allergy.
A history of reaction versions is returned only for reactions with changes, or a new reaction. This value can be null.
-
reviewInfo:
object ReviewInfo
The information around who and when the data was reviewed.
Nested Schema : allergyFieldUpdates
Type:
arrayThe list of changes made to allergy fields in the current instance. This value can be null.
Show Source
-
Array of:
object UpdatedAllergyField
A record of the change to an allergy version.
Nested Schema : AllergySummary
Type:
objectThe summary of an allergy that contains only important information about the allergy.
Show Source
-
createdBy(required):
object PersonSimple
A simple representation of the individual person that was retrieved. The individual could be a personnel member (provider), a patient, or a nonpatient person.
-
createdDateTime(required):
string(date-time)
The date and time that the allergy was created in the ISO-8601 representation of the date and time format (YYYY-MM-DDTHH:MM:SS:SSSZ) as defined by RFC 3339.Example:
2018-06-16T21:31:35.457Z -
id(required):
string
The unique identifier of the allergy.
-
lastModifiedBy(required):
object PersonSimple
A simple representation of the individual person that was retrieved. The individual could be a personnel member (provider), a patient, or a nonpatient person.
-
lastModifiedDateTime(required):
string(date-time)
The date and time that the allergy was last modified in the ISO-8601 representation of the date and time format (YYYY-MM-DDTHH:MM:SS:SSSZ) as defined by RFC 3339.Example:
2018-06-16T21:31:35.457Z -
patient(required):
object PersonSimple
A simple representation of the individual person that was retrieved. The individual could be a personnel member (provider), a patient, or a nonpatient person.
-
substance(required):
object NomenclatureOrFreetextValue
The nomenclature or free text value of the data.
-
version(required):
string
The unique identifier of the instance for this allergy.
Nested Schema : Combine
Type:
objectThe details of where the changes to an allergy based on a combine came from.
Show Source
-
allergyId(required):
string
The identifier of the allergy that was combined.
-
combinedPatient(required):
object PersonSimple
A simple representation of the individual person that was retrieved. The individual could be a personnel member (provider), a patient, or a nonpatient person.
Nested Schema : DateTimePeriodWithoutZone
Type:
objectA representation of a date and time range without time zone information.
Show Source
-
endDateTime:
string(date-time)
The date and time represented in YYYY-MM-DDTHH:MM:SS:SSSZ format without the UTC offset as defined by RFC 3339. No time zone information is associated with this date and time.Example:
2018-06-16T21:31:35.457Z -
startDateTime:
string(date-time)
The date and time represented in YYYY-MM-DDTHH:MM:SS:SSSZ format without the UTC offset as defined by RFC 3339. No time zone information is associated with this date and time.Example:
2018-06-16T21:31:35.457Z
Nested Schema : PersonSimple
Type:
objectA simple representation of the individual person that was retrieved.
The individual could be a personnel member (provider), a patient, or a nonpatient person.
Show Source
-
id(required):
string
The unique identifier for the individual.
-
name:
object PersonNameSummary
A summary of just first, last, and full name for a person (which could be a personnel member, patient, or nonpatient person).
Nested Schema : reactionVersions
Type:
arrayThe versions of reactions associated with the current allergy.
A history of reaction versions is returned only for reactions with changes, or a new reaction. This value can be null.
-
Array of:
object ReactionVersion
A version of a reaction.
Nested Schema : ReviewInfo
Type:
objectThe information around who and when the data was reviewed.
Show Source
-
reviewedBy(required):
object PersonSimple
A simple representation of the individual person that was retrieved. The individual could be a personnel member (provider), a patient, or a nonpatient person.
-
reviewedDateTime(required):
object DateTimeWithZone
A representation of the date and time with the time zone.
Nested Schema : UpdatedAllergyField
Type:
objectA record of the change to an allergy version.
Show Source
-
currentValue(required):
string
The current value of the field.
-
field(required):
string
Allowed Values:
[ "CANCEL_REASON", "INFO_SOURCE", "CRITICALITY", "STATUS", "CATEGORY", "REACTION_TYPE", "ONSET_DATETIME", "ONSET_PRECISION", "ONSET_UNIT" ]The name of the field that has changed. -
previousValue:
string
The previous value of the field.
Nested Schema : NomenclatureOrFreetextValue
Type:
objectThe nomenclature or free text value of the data.
Show Source
-
freeText:
string
The free text display of the data. This display is returned only if the type is
FREE_TEXT. -
nomenclature:
object NomenclatureSimple
The model object for a nomenclature.
-
type(required):
string
Allowed Values:
[ "NOMENCLATURE", "FREE_TEXT" ]The type of value the data is captured as.
Nested Schema : NomenclatureSimple
Type:
objectThe model object for a nomenclature.
Show Source
-
code:
string
The universal clinical code of the term.Example:
452.5b -
conceptCki:
string
The concept CKI of the nomenclature.
-
displayName:
string
The display of the nomenclature.Example:
Anemia Nomenclature -
id(required):
string
The unique identifier of the nomenclature.Example:
1643574645 -
terminology:
object CodeValueSimple
A minimal representation of a code value.
-
terminologyAxis:
object CodeValueSimple
A minimal representation of a code value.
Nested Schema : CodeValueSimple
Type:
objectA minimal representation of a code value.
Show Source
-
cdfMeaning:
string
A programmatic value, primarily used by applications to search for this value.
-
display:
string
The text consumers see that represents this code value.
-
id(required):
string
The ID of the code value.
Nested Schema : PersonNameSummary
Type:
objectA summary of just first, last, and full name for a person (which could be a personnel member, patient, or nonpatient person).
Show Source
-
firstName:
string
The person's first given name.
-
fullName:
string
The fully formatted name.
-
lastName:
string
The person's family last name.
Nested Schema : ReactionVersion
Type:
objectA version of a reaction.
Show Source
-
isNew:
boolean
Identifies if this reaction is a new reaction.
-
symptom:
object NomenclatureOrFreetextValue
The nomenclature or free text value of the data.
-
versionsOfUpdatedReactionFields:
array versionsOfUpdatedReactionFields
The set of changes for this reaction.
Nested Schema : versionsOfUpdatedReactionFields
Type:
arrayThe set of changes for this reaction.
Show Source
-
Array of:
object UpdatedReactionField
A record of the change to a reaction version.
Nested Schema : UpdatedReactionField
Type:
objectA record of the change to a reaction version.
Show Source
-
currentValue(required):
string
The current value of the field.
-
field(required):
string
Allowed Values:
[ "SEVERITY", "IS_ACTIVE" ]The name of the field that was updated. -
previousValue:
string
The previous value of the field.
Nested Schema : DateTimeWithZone
Type:
objectA representation of the date and time with the time zone.
Show Source
-
dateTime:
string(date-time)
The date and time represented in YYYY-MM-DDTHH:MM:SS:SSSZ format without the UTC offset as defined by RFC 3339. No timezone information is associated with this date/time.
-
ianaTimeZone:
string
The time zone, provided that the date includes time precision. If
dateTimecontains time, then this field is required.
400 Response
Bad Request
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
401 Response
Unauthorized
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
403 Response
NotAuthorized
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
404 Response
Not Found
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
429 Response
Too Many Requests
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
500 Response
Internal Server Error
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.