Patient Profile

This Patient profile is part of the set of resource profiles supported by the API Server used with the athenaPractice 12.3 and athenaFlow 9.12 products. It further describes read, search, create and update capabilities of these products.

Overview

This resource captures basic and administrative information for an individual receiving care or other health-related services.

Scope and Usage

This profile is used to define the content that will be returned by the API Server in response to requests to access Patient resources. All elements listed in the differential profile view are Supported, which means that the API Server is capable of supplying these fields from the product database when they have been populated via the product or its APIs.

The profile also defines the content that must be supplied to the API Server in response to requests to populate Patient resources. Fields which are marked as Mandatory in this profile are those that must be supplied to the API Server in content used to populate a resource.

Source

The Patient resource derives from the PatientProfile table in athenaPractice, and the PERSON table in athenaFlow Specific detail can be found in the Mappings section below.

Supported Operations

The operations supported by this resource are listed below.

Read Operation

Read operations are executed as specified in the HL7 FHIR RESTful API implementation definition. To read a Patient, an application shall perform an HTTP GET, specifying the identifier of the resources being retrieved.

GET [base]/fhir/Patient/[id]{?_format=[json|xml]&_summary=[true|data]}

Read Operation Parameters

ParameterDescription
[base]Specifies the base URL of the FHIR Server, e.g., https://cpsapisandbox.virenceaz.com:9443/demoAPIServer
[id]Specifies the identifier of the Patient resource to retrieve
[_format]Specifies the format of the output and may be xml or json. When present, the _format value overrides the value of the Accept header in the request.
[_summary]Filters the output to include only summary elements (_summary=true) or to omit the generated narrative (_summary=data). Note: If the generated html narrative for the resource is not going to be used by the call, using _summary=data provides slightly improved API response times.

Read Operation HTTP Response Codes

Response CodeDescription
200 OKThe requested resource was found and is contained within the body of the HTTP response.
401 UnauthorizedAuthorization is required for this request, and either the Authorization header is missing or the supplied user credentials in the Authorization header are not valid or have expired. The body of the HTTP response will contain an OperationOutcome resource that indicates that Authorization is required.
404 Not FoundThe requested resource does not exist. The body of the HTTP response will contain an OperationOutcome resource that indicates that the resource could not be found.
500 Server ErrorThe server may return other error codes to indicate other error conditions. The body of the HTTP response will contain an OperationOutcome resource that indicates the nature of the error.

Search Operation

Search operations are executed as specified in the HL7 FHIR RESTful API implementation definition. To search for Patient resources, an application shall perform an HTTP GET, specifying the query parameters associated with the resource.

GET [base]/fhir/Patient?{search-parameters}{&_count=[max-results]&_format=[json|xml]&_summary=[true|text|data]}

Search Operation Parameters

ParameterDescription
[base]Specifies the base URL of the FHIR Server, e.g., https://cpsapisandbox.virenceaz.com:9443/demoAPIServer
[_count]Specifies the maximum number of search results to return in a single query. Note: The count of results does not limit the number of additional resources returned via the _include parameter. No more than max-results Patient resources which match the search criteria will be returned. The API Server has default and maximum limits for the value that can be specified for this parameter. These limits may vary depending upon the client application vendors participation level in the AthenaHealth Partner program. Note: The API Server support the HL7 FHIR Paging capability.
[_format]Specifies the format of the output and may be xml or json. When present, the _format value overrides the value of the Accept header in the request.
[_summary]Filters the output to include only narrative elements (_summary=text), summary elements (_summary=true) or to omit the generated narrative (_summary=data). Note: If the generated html narrative for the resource is not going to be used by the call, using _summary=data provides improved API response times, especially when returning larger result sets.
_id (token )The ID of the resource
_lastUpdated (date )
_lastUpdated-fromnow (quantity )Like _lastUpdated except expressed as a positive or negative offset from the current time in units of time , e.g. _lastUpdated-fromnow=ge7||d for more than seven days in the future or =le-2||mo for less than two months in the past. The unit must be specified.
_security (token )
active (token )Whether the patient record is active
address-city (string )A city specified in an address
address-country (string )A country specified in an address
address-postalcode (string )A postalCode specified in an address
address-state (string )A state specified in an address
birthdate (date )The patient's date of birth
birthdate-fromnow (quantity )Like birthdate except expressed as a positive or negative offset from the current time in units of time , e.g. birthdate-fromnow=ge7||d for more than seven days in the future or =le-2||mo for less than two months in the past. The unit must be specified.
careprovider (reference )Patient's nominated care provider, could be a care manager, not the organization that manages the record
deathdate (date )The date of death has been provided and satisfies this search value
deathdate-fromnow (quantity )Like deathdate except expressed as a positive or negative offset from the current time in units of time , e.g. deathdate-fromnow=ge7||d for more than seven days in the future or =le-2||mo for less than two months in the past. The unit must be specified.
deceased (token )This patient has been marked as deceased, or as a death date entered
email (token )A value in an email contact
ethnicity (token )
family (string )A portion of the family name of the patient
gender (token )Gender of the patient
genderIdentity (token )
given (string )A portion of the given name of the patient
identifier (token )A patient identifier
language (token )Language code (irrespective of use value)
mothersMaidenName (string )
name (string )A portion of either family or given name of the patient
organization (reference )The organization at which this person is a patient
phone (token )A value in a phone contact
phonetic (string )A portion of either family or given name using some kind of phonetic matching algorithm
race (token )
sexualOrientation (token )
telecom (token )The value in any kind of telecom details of the patient

Search Operation HTTP Response Codes

Response CodeDescription
200 OKThe query was performed and any results found are contained within the body of the HTTP response. Note: The search API will return 200 OK when the query itself is successful, regardless of whether or not any matching results were found.
401 UnauthorizedAuthorization is required for this request, and either the Authorization header is missing or the supplied user credentials in the Authorization header are not valid or have expired. The body of the HTTP response will contain an OperationOutcome resource that indicates that Authorization is required.
500 Server ErrorThe server may return other error codes to indicate other error conditions. The body of the HTTP response will contain an OperationOutcome resource that indicates the nature of the error.

Create Operation

Create operations are executed as specified in the HL7 FHIR RESTful API implementation definition. To create a new Patient resource, an application must perform an HTTP POST, specifying the content of the resource in the body of the request.

POST [base]/fhir/Patient?{_format=[json|xml]}

Create Operation Parameters

ParameterDescription
[_format]Specifies the format of the output and may be xml or json. When present, the _format value overrides the value of the Accept header in the request.

Create Operation HTTP Response Codes

Response CodeDescription
201 CreatedThe resource was created at the location specified in the HTTP Location header. Note: Unsupported fields will be accepted in a request but will not be persisted to the database. Some fields may be mapped to database specific codes which closely but not perfectly match the input. See the HL7 FHIR specification for more detail on server permitted changes.
400 Bad RequestThe resource could not be parsed, or failed basic validation rules. The body of the HTTP response will contain an OperationOutcome resource that provide more detail about the reason for the failure.
401 UnauthorizedAuthorization is required for this request, and either the Authorization header is missing or the supplied user credentials in the Authorization header are not valid or have expired. The body of the HTTP response will contain an OperationOutcome resource that indicates that Authorization is required.
422 Unprocessable EntityThe proposed resource violated server business rules. For example, a required field may be missing or a field may contain a value that is not supported by the API Server. The body of the HTTP response will contain an OperationOutcome resource that provide more detail about the reason for the failure.
500 Server ErrorThe server may return other error codes to indicate other error conditions. The body of the HTTP response will contain an OperationOutcome resource that indicates the nature of the error.

Update Operation

Update operations are executed as specified in the HL7 FHIR RESTful API implementation definition. To create a new Patient resource, an application must perform an HTTP PUT, specifying the content of the resource in the body of the request.

PUT [base]/fhir/Patient/[id]?{_format=[json|xml]}

Update Operation Parameters

ParameterDescription
[_format]Specifies the format of the output and may be xml or json. When present, the _format value overrides the value of the Accept header in the request.

Update Operation HTTP Response Codes

Response CodeDescription
200 OKThe resource was updated at the location specified in the HTTP Location header. Note: Unsupported fields will be accepted in a request but will not be persisted to the database. Some fields may be mapped to database specific codes which closely but not perfectly match the input. See the HL7 FHIR specification for more detail on server permitted changes.
400 Bad RequestThe resource could not be parsed, or failed basic validation rules. The body of the HTTP response will contain an OperationOutcome resource that provide more detail about the reason for the failure.
401 UnauthorizedAuthorization is required for this request, and either the Authorization header is missing or the supplied user credentials in the Authorization header are not valid or have expired. The body of the HTTP response will contain an OperationOutcome resource that indicates that Authorization is required.
422 Unprocessable EntityThe proposed resource violated server business rules. For example, a required field may be missing or a field may contain a value that is not supported by the API Server. The body of the HTTP response will contain an OperationOutcome resource that provide more detail about the reason for the failure.
500 Server ErrorThe server may return other error codes to indicate other error conditions. The body of the HTTP response will contain an OperationOutcome resource that indicates the nature of the error.

Other Operations

This Implementation guide defines 2 operations:

$ihe-pix Mobile Patient Identifier Cross-reference Query [ITI-83]
$unique Find Unique Patient

For more information about operations, including how they are invoked, see Operations .

Mobile Patient Identifier Cross-reference Query [ITI-83]

Look up patient identifiers.

GET [base]/$ihe-pix?{operation-parameters}
In Parameters:
NameCardinalityTypeBindingProfileDocumentation
sourceIdentifier1..1token

The source identifier for the patient [required].

targetSystem0..1uri

The target identifier space [optional].

Out Parameters:
NameCardinalityTypeBindingProfileDocumentation
targetIdentifier0..*Identifier

The identifier found.

targetId0..*Reference (Patient )

The URL of the Patient Resource.

This operation implements the [ITI-83] Mobile Patient Identifier Cross-reference Query transaction specified in the <a target="blank" href="http://www.ihe.net/uploadedFiles/Documents/ITI/IHEITISupplPIXm.pdf">IHE PIXm</a> profile. It is used by the Patient Identifier Cross-reference Consumer to solicit information about patients whose Patient Identifiers cross-match with Patient Identifiers provided in the query parameters of the request message. The request is received by the Patient Identifier Crossreference Manager. The Patient Identifier Cross-reference Manager processes the request and returns a response in the form of zero or more Patient Identifiers for the matching patient.

 

Find Unique Patient

Locates a unique patient by demographics or returns an error or none or more than one found.

GET [base]/$unique?{operation-parameters}
In Parameters:
NameCardinalityTypeBindingProfileDocumentation
birthdate1..1date

The birthdate of this patient [required]

family1..1string

The last name of this patient [required]

gender1..1token

The gender of this patient [required]

given1..1string

The first or middle name for this patient [required]

address-postalcode0..1string

The zip code of the patient [optional]

email0..1token

The email address for this patient [optional]

identifier0..1token

Any other identifier known for this patient [optional]

phone0..1token

A phone number for this patient [optional]

telecom0..1token

A phone number or email address for this patient [optional]

Out Parameters:
NameCardinalityTypeBindingProfileDocumentation
return1..1Patient

The patient that was found.

Note: as this the only out parameter, it is a resource, and it has the name 'return', the result of this operation is returned directly as a resource

This operation is used to identify a unique patient based on known patient demographics.

 

Profile Content

The official URL for this profile is:

http://hl7.org/fhir/StructureDefinition/patient-profile

Information about an individual receiving health care services

Name Flags Card. Type Description & Constraints
.. Patient0..*Patient Information about an individual receiving health care services
... meta0..1Meta Metadata about the resource
... implicitRules?! 0..1uri A set of rules under which this content was created
... language0..1code Language of the resource content

Binding: IETF BCP-47 (required )
... textI0..1Narrative Text summary of the resource, for human interpretation
... contained0..*Resource Contained, inline Resources
... us-core-raceS0..1CodeableConcept Extension
... us-core-ethnicityS0..1CodeableConcept Extension
... patient-mothersMaidenNameS0..1string Extension
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/patient-mothersMaidenName"
.... valueString1..1string Value of extension
...patient-extension-RESPPROVID0..1Reference (Reference)Extension
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/patient-extension-RESPPROVID"
.... valueReference1..1Reference (Reference)Value of extension
...patient-extension-REFDOCID0..1Reference (Reference)Extension
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/patient-extension-REFDOCID"
.... valueReference1..1Reference (Reference)Value of extension
...patient-extension-preferredContactS0..1string Extension
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/patient-extension-preferredContact"
.... valueString1..1string Value of extension
... patient-birthTimeS0..1dateTime Extension
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/patient-birthTime"
.... valueDateTime1..1dateTime Value of extension
...patient-extension-patientAsGuarantorS0..1boolean Extension
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/patient-extension-patientAsGuarantor"
.... valueBoolean1..1boolean Value of extension
...patient-extension-genderIdentityS0..1string Extension
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/patient-extension-genderIdentity"
.... valueString1..1string Value of extension
...patient-extension-sexualOrientationS0..1string Extension
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/patient-extension-sexualOrientation"
.... valueString1..1string Value of extension
...patient-extension-guarantorDetailsS0..1Reference (Reference)Extension
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/patient-extension-guarantorDetails"
.... valueReference1..1Reference (Reference)Value of extension
... extensionS0..1?? [UriType[http://fhir.org/guides/argonaut/StructureDefinition/argo-race]]Extensionhttp://fhir.org/guides/argonaut/StructureDefinition/argo-race
... extensionS0..1?? [UriType[http://fhir.org/guides/argonaut/StructureDefinition/argo-ethnicity]]Extensionhttp://fhir.org/guides/argonaut/StructureDefinition/argo-ethnicity
... extensionS0..1?? [UriType[http://fhir.org/guides/argonaut/StructureDefinition/argo-birthsex]]Extensionhttp://fhir.org/guides/argonaut/StructureDefinition/argo-birthsex
... modifierExtension?!0..*Extension Extensions that cannot be ignored
... identifierIdentifier An identifier for this patient

Slice: Unordered, Closed, by type
... identifierS 1..*Identifier An identifier for this patient
... identifierS 0..1Identifier An identifier for this patient
.... extension0..*Extension Additional Content defined by implementations
.... use?! 0..1code usual | official | temp | secondary (If known)

Binding: IdentifierUse (required )
.... typeS 1..1CodeableConcept Description of identifier

Binding: Identifier Type Codes (extensible )
..... extension0..*Extension Additional Content defined by implementations
..... coding1..1Coding Code defined by a terminology system
...... extension0..*Extension Additional Content defined by implementations
...... system1..1uri Identity of the terminology system

Fixed Value: http://hl7.org/fhir/v2/0203
...... version0..1string Version of the system - if relevant
...... code1..1code Symbol in syntax defined by the system

Fixed Value: PI
...... display0..1string Representation defined by the system
...... userSelected0..1boolean If this coding was chosen directly by the user
..... text0..1string Plain text representation of the concept
.... systemS 1..1uri The namespace for the identifier

Example: http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
.... valueS 1..1string The value that is unique

Example: 123456
.... period0..1Period Time period when id is/was valid for use
.... assigner0..1Reference (Organization )Organization that issued id (may be just text)
... identifier0..1Identifier An identifier for this patient
.... extension0..*Extension Additional Content defined by implementations
.... use?! 1..1code usual | official | temp | secondary (If known)

Binding: IdentifierUse (required )

Fixed Value: secondary
.... typeS 0..1CodeableConcept Description of identifier

Binding: Identifier Type Codes (extensible )
..... extension0..*Extension Additional Content defined by implementations
..... coding1..1Coding Code defined by a terminology system
...... extension0..*Extension Additional Content defined by implementations
...... system1..1uri Identity of the terminology system

Fixed Value: http://hl7.org/fhir/identifier-type
...... version0..1string Version of the system - if relevant
...... code1..1code Symbol in syntax defined by the system

Fixed Value: SB
...... display0..1string Representation defined by the system
...... userSelected0..1boolean If this coding was chosen directly by the user
..... text0..1string Plain text representation of the concept
.... systemS 1..1uri The namespace for the identifier

Fixed Value: http://hl7.org/fhir/sid/us-ssn
.... valueS 1..1string The value that is unique

Example: 123456
.... period0..1Period Time period when id is/was valid for use
.... assigner0..1Reference (Organization )Organization that issued id (may be just text)
... identifier0..1Identifier An identifier for this patient
.... extension0..*Extension Additional Content defined by implementations
.... use?! 0..1code usual | official | temp | secondary (If known)

Binding: IdentifierUse (required )
.... typeS 0..1CodeableConcept Description of identifier

Binding: Identifier Type Codes (extensible )
..... extension0..*Extension Additional Content defined by implementations
..... coding1..1Coding Code defined by a terminology system
...... extension0..*Extension Additional Content defined by implementations
...... system1..1uri Identity of the terminology system

Fixed Value: http://hl7.org/fhir/v2/0203
...... version0..1string Version of the system - if relevant
...... code1..1code Symbol in syntax defined by the system

Fixed Value: MR
...... display0..1string Representation defined by the system
...... userSelected0..1boolean If this coding was chosen directly by the user
..... text0..1string Plain text representation of the concept
.... systemS 1..1uri The namespace for the identifier

Example: http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
.... valueS 1..1string The value that is unique

Example: 123456
.... period0..1Period Time period when id is/was valid for use
.... assigner0..1Reference (Organization )Organization that issued id (may be just text)
... identifier0..*Identifier An identifier for this patient
... active?! S0..1boolean Whether this patient's record is in active use
... nameHumanName A name associated with the patient

Slice: Unordered, Open, by USUALNAME
... nameS 1..2HumanName A name associated with the patient
.... extension0..*Extension Additional Content defined by implementations
.... use?! 0..1code usual | official | temp | nickname | anonymous | old | maiden

Binding: NameUse (required )

Fixed Value: official
.... text0..1string Text representation of the full name
.... family0..1string Family name (often called 'Surname')
.... givenstring Given names (not always 'first'). Includes middle names

Slice: Ordered, Closed, by given
.... given0..2string Given names (not always 'first'). Includes middle names
.... given0..1string Given names (not always 'first'). Includes middle names
.... given0..1string Given names (not always 'first'). Includes middle names
.... prefix0..1string Parts that come before the name
.... suffix0..1string Parts that come after the name
.... period0..1Period Time period when name was/is in use
... nameS 1..2HumanName A name associated with the patient
.... extension0..*Extension Additional Content defined by implementations
.... use?! 0..1code usual | official | temp | nickname | anonymous | old | maiden

Binding: NameUse (required )
.... text0..1string Text representation of the full name
.... family0..*string Family name (often called 'Surname')
.... given0..1string Given names (not always 'first'). Includes middle names
.... prefix0..*string Parts that come before the name
.... suffix0..*string Parts that come after the name
.... period0..1Period Time period when name was/is in use
... telecomContactPoint A contact detail for the individual

Slice: Unordered, Closed, by type use
... telecomS 0..6ContactPoint A contact detail for the individual
... telecom0..1ContactPoint A contact detail for the individual
.... extension0..*Extension Additional Content defined by implementations
.... systemS I1..1code phone | fax | email | pager | other

Binding: ContactPointSystem (required )

Fixed Value: phone
.... valueS 1..1string The actual contact point details
.... use?! S0..1code home | work | temp | old | mobile - purpose of this contact point

Binding: ContactPointUse (required )

Fixed Value: work
.... rank0..1positiveInt Specify preferred order of use (1 = highest)
.... period0..1Period Time period when the contact point was/is in use
... telecom0..1ContactPoint A contact detail for the individual
.... extension0..*Extension Additional Content defined by implementations
.... systemS I1..1code phone | fax | email | pager | other

Binding: ContactPointSystem (required )

Fixed Value: phone
.... valueS 1..1string The actual contact point details
.... use?! S0..1code home | work | temp | old | mobile - purpose of this contact point

Binding: ContactPointUse (required )

Fixed Value: home
.... rank0..1positiveInt Specify preferred order of use (1 = highest)
.... period0..1Period Time period when the contact point was/is in use
... telecom0..1ContactPoint A contact detail for the individual
.... extension0..*Extension Additional Content defined by implementations
.... systemS I1..1code phone | fax | email | pager | other

Binding: ContactPointSystem (required )

Fixed Value: phone
.... valueS 1..1string The actual contact point details
.... use?! S0..1code home | work | temp | old | mobile - purpose of this contact point

Binding: ContactPointUse (required )

Fixed Value: mobile
.... rank0..1positiveInt Specify preferred order of use (1 = highest)
.... period0..1Period Time period when the contact point was/is in use
... telecom0..1ContactPoint A contact detail for the individual
.... extension0..*Extension Additional Content defined by implementations
.... systemS I1..1code phone | fax | email | pager | other

Binding: ContactPointSystem (required )

Fixed Value: fax
.... valueS 1..1string The actual contact point details
.... rank0..1positiveInt Specify preferred order of use (1 = highest)
.... period0..1Period Time period when the contact point was/is in use
... telecom0..1ContactPoint A contact detail for the individual
.... extension0..*Extension Additional Content defined by implementations
.... systemS I1..1code phone | fax | email | pager | other

Binding: ContactPointSystem (required )

Fixed Value: pager
.... valueS 1..1string The actual contact point details
.... use?! 0..1code home | work | temp | old | mobile - purpose of this contact point

Binding: ContactPointUse (required )
.... rank0..1positiveInt Specify preferred order of use (1 = highest)
.... period0..1Period Time period when the contact point was/is in use
... telecom0..1ContactPoint A contact detail for the individual
.... extension0..*Extension Additional Content defined by implementations
.... systemS I1..1code phone | fax | email | pager | other

Binding: ContactPointSystem (required )

Fixed Value: email
.... valueS 1..1string The actual contact point details
.... use?! 0..1code home | work | temp | old | mobile - purpose of this contact point

Binding: ContactPointUse (required )
.... rank0..1positiveInt Specify preferred order of use (1 = highest)
.... period0..1Period Time period when the contact point was/is in use
... genderS 0..1code male | female | other | unknown

Binding: AdministrativeGender (required )
... birthDateS 0..1date The date of birth for the individual
... deceased[x]?! S0..1boolean , dateTime Indicates if the individual is deceased or not
... addressS 0..1Address Addresses for the individual
.... extension0..*Extension Additional Content defined by implementations
.... use?! 0..1code home | work | temp | old - purpose of this address

Binding: AddressUse (required )

Example: home
.... type0..1code postal | physical | both

Binding: AddressType (required )

Example: both
.... text0..1string Text representation of the address

Example: 137 Nowhere Street, Erewhon 9132
.... linestring Street name, number, direction & P.O. Box etc.

Slice: Ordered, Closed, by line

Example: 137 Nowhere Street
.... line0..2string Street name, number, direction & P.O. Box etc.

Example: 137 Nowhere Street
.... line0..1string Street name, number, direction & P.O. Box etc.

Example: 137 Nowhere Street
.... line0..1string Street name, number, direction & P.O. Box etc.

Example: 137 Nowhere Street
.... city0..1string Name of city, town etc.

Example: Erewhon
.... district0..1string District name (aka county)

Example: Madison
.... state0..1string Sub-unit of country (abbreviations ok)
.... postalCode0..1string Postal code for area

Example: 9132
.... country0..1string Country (can be ISO 3166 3 letter code)
.... period0..1Period Time period when address was/is in use

Example: {"start":"2010-03-23","end":"2010-07-01"}
... maritalStatusS0..1CodeableConcept Marital (civil) status of a patient

Binding: Marital Status Codes (required )
... multipleBirth[x]0..1boolean , integer Whether patient is part of a multiple birth
... photo0..*Attachment Image of the patient
... contactI0..*BackboneElement A contact party (e.g. guardian, partner, friend) for the patient

pat-1: SHALL at least contain a contact's details or a reference to an organization
.... extension0..*Extension Additional Content defined by implementations
.... modifierExtension?!0..*Extension Extensions that cannot be ignored
.... relationship0..*CodeableConcept The kind of relationship

Binding: PatientContactRelationship (extensible )
.... name0..1HumanName A name associated with the contact person
.... telecom0..*ContactPoint A contact detail for the person
.... address0..1Address Address for the contact person
.... gender0..1code male | female | other | unknown

Binding: AdministrativeGender (required )
.... organizationI0..1Reference (Organization )Organization that is associated with the contact
.... period0..1Period The period during which this contact person or organization is valid to be contacted relating to this patient
... animal?! 0..1BackboneElement This patient is known to be an animal (non-human)
.... extension0..*Extension Additional Content defined by implementations
.... modifierExtension?!0..*Extension Extensions that cannot be ignored
.... species1..1CodeableConcept E.g. Dog, Cow

Binding: AnimalSpecies (example )
.... breed0..1CodeableConcept E.g. Poodle, Angus

Binding: AnimalBreeds (example )
.... genderStatus0..1CodeableConcept E.g. Neutered, Intact

Binding: GenderStatus (example )
... communication0..*BackboneElement A list of Languages which may be used to communicate with the patient about his or her health
.... extension0..*Extension Additional Content defined by implementations
.... modifierExtension?!0..*Extension Extensions that cannot be ignored
.... language1..1CodeableConcept The language which can be used to communicate with the patient about his or her health

Binding: IETF BCP-47 (required )
.... preferred0..1boolean Language preference indicator
... careProvider0..*Reference (Practitioner )Patient's nominated primary care provider
... managingOrganization0..1Reference (Organization )Organization that is the custodian of the patient record
... link?!0..*BackboneElement Link to another patient resource that concerns the same actual person
.... extension0..*Extension Additional Content defined by implementations
.... modifierExtension?!0..*Extension Extensions that cannot be ignored
.... other?!1..1Reference (Patient )The other patient resource that the link refers to
.... type?!1..1code replace | refer | seealso - type of link

Binding: LinkType (required )


 

athenaPractice Mapping

The mappings in this section represent the how data stored within athenaPractice is served through the product's APIs. athenaPractice and athenaFlow share a common schema for patient clinical data and only one is shown when these are the same. Use of this information is subject to the API Server Terms and Conditions .

Patient Profile
PatientPatient-ProfileFHIR_PATIENTVIEW
 ├ idPIDMakeId(%PID%)
 ├ extensionPATIENTRACEMIDMakeExtensionList(%RACE%,"RACE","http://hl7.org/fhir/StructureDefinition/us-core-race")
 ├ extensionETHNICITYMIDMakeExtensionList(%ETHNICITY%,"ETHNICITY","http://hl7.org/fhir/StructureDefinition/us-core-ethnicity")
 ├ extensionmothersMaidenName
 ├ extensionRESPPROVID
 ├ extensionREFDOCID
 ├ extensionpreferredContact
 ├ extensionBIRTHTIME
 ├ extensionpatientAsGuarantor
 ├ extensiongenderIdentity
 ├ extensionsexualOrientation
 ├ extensionguarantorDetails
 ├ extensionARGORACEMIDMakeCodingExtension(%RACE%,"RACE","http://fhir.org/guides/argonaut/StructureDefinition/argo-race")
 ├ extensionARGOETHNICITYMIDMakeCodingExtension(%ETHNICITY%,"ETHNICITY","http://fhir.org/guides/argonaut/StructureDefinition/argo-ethnicity")
 ├ extensionbirthsexMakeCodeExtension(%SEX%, "http://fhir.org/guides/argonaut/StructureDefinition/argo-birthsex")
 ├ identifierPatient Identifiers
 ├ identifierPATIENTID
  │ ├ systemgetSiteIdSystem("PatientId")
  │ └ value%PATIENTID%
 ├ identifierSOCSECNO
  │ └ value%SOCSECNO%
 ├ identifierMEDRECNO
  │ ├ systemgetSiteIdSystem("MRN")
  │ └ value%MEDRECNO%
 ├ identifierEXTID
 ├ activePSTATUSEquals("A",%PSTATUS%)
 ├ nameUSUALNAMEMakeSearchName(%TITLE%,%FIRSTNAME%,%MIDDLENAME%,%LASTNAME%,%ENTITLEMENTS%)
  │ ├ familyLASTNAME%LASTNAME%
  │ ├ givenGiven Names
  │ ├ givenFIRSTNAME%FIRSTNAME%
  │ ├ givenMIDDLENAME%MIDDLENAME%
  │ ├ prefixTITLE%TITLE%
  │ └ suffixENTITLEMENTS%ENTITLEMENTS%
 ├ nameNICKNAME
  │ ├ use"nickname"
  │ └ given%NICKNAME%
 ├ telecomPhone Numbers
 ├ telecomWORKPHONE
  │ └ value%WORKPHONE%
 ├ telecomALTPHONE
  │ └ value%ALTPHONE%
 ├ telecomCELLPHONE
  │ └ value%CELLPHONE%
 ├ telecomFAXPHONE
  │ └ value%FAXPHONE%
 ├ telecomPAGERPHONE
  │ └ value%PAGERPHONE%
 ├ telecomEMAIL
  │ └ value%EMAIL%
 ├ genderSEXMapCode(%SEX%,"GENDER")
 ├ birthDateDATEOFBIRTH%DATEOFBIRTH%
 ├ deceased[x]DATEOFDEATHIfNull(%DATEOFDEATH%).Then(Equals("X",%PSTATUS%)) | IfSet(%DATEOFDEATH%).Then(%DATEOFDEATH%)
 ├ addressADDRESSMakeSearchAddress(%ADDRESS1%,%ADDRESS2%,%CITY%,%STATE%,%ZIP%,%COUNTRY%)
  │ ├ lineAddress Lines
  │ ├ lineADDRESS1%ADDRESS1%
  │ ├ lineADDRESS2%ADDRESS2%
  │ ├ cityCITY%CITY%
  │ ├ stateSTATE%STATE%
  │ ├ postalCodeZIP%ZIP%
  │ └ countryCOUNTRY%COUNTRY%
 ├ maritalStatusMARITALSTATUSMapConcept(%MARITALSTATUS%,"MARITALSTATUS")
 ├ photoPHOTO_IDMakeBinary("Photo",%PHOTO_ID%)
 ├ communicationLANGCODE
  │ ├ languageMakeConcept(%LANGCODE%,"urn:ietf:bcp:47",%PREFLANG%)
  │ └ preferredtrue
 ├ careProviderPrimaryCareProviderMakeReference("USR",%PRICAREID%,"Practitioner")
 └ managingOrganizationHOMELOCATIONMakeReference("LOCREG",%HOMELOCATION%,"Organization")

athenaFlow Mapping

The mappings in this section represent the how data stored within athenaFlow is served through the product's APIs. Use of this information is subject to the API Server Terms and Conditions .

Patient Profile
PatientPatient-ProfileFHIR_PATIENTVIEW
 ├ idPIDMakeId(%PID%)
 ├ extensionPATIENTRACEMIDMakeExtensionList(%RACE%,"RACE","http://hl7.org/fhir/StructureDefinition/us-core-race")
 ├ extensionETHNICITYMIDMakeExtensionList(%ETHNICITY%,"ETHNICITY","http://hl7.org/fhir/StructureDefinition/us-core-ethnicity")
 ├ extensionmothersMaidenName
 ├ extensionRESPPROVID
 ├ extensionREFDOCID
 ├ extensionpreferredContact
 ├ extensionBIRTHTIME
 ├ extensionpatientAsGuarantor
 ├ extensiongenderIdentity
 ├ extensionsexualOrientation
 ├ extensionguarantorDetails
 ├ extensionARGORACEMIDMakeCodingExtension(%RACE%,"RACE","http://fhir.org/guides/argonaut/StructureDefinition/argo-race")
 ├ extensionARGOETHNICITYMIDMakeCodingExtension(%ETHNICITY%,"ETHNICITY","http://fhir.org/guides/argonaut/StructureDefinition/argo-ethnicity")
 ├ extensionbirthsexMakeCodeExtension(%SEX%, "http://fhir.org/guides/argonaut/StructureDefinition/argo-birthsex")
 ├ identifierPatient Identifiers
 ├ identifierPATIENTID
  │ ├ systemgetSiteIdSystem("PatientId")
  │ └ value%PATIENTID%
 ├ identifierSOCSECNO
  │ └ value%SOCSECNO%
 ├ identifierMEDRECNO
  │ ├ systemgetSiteIdSystem("MRN")
  │ └ value%MEDRECNO%
 ├ identifierEXTID
 ├ activePSTATUSEquals("A",%PSTATUS%)
 ├ nameUSUALNAMEMakeSearchName(%TITLE%,%FIRSTNAME%,%MIDDLENAME%,%LASTNAME%,%ENTITLEMENTS%)
  │ ├ familyLASTNAME%LASTNAME%
  │ ├ givenGiven Names
  │ ├ givenFIRSTNAME%FIRSTNAME%
  │ ├ givenMIDDLENAME%MIDDLENAME%
  │ ├ prefixTITLE%TITLE%
  │ └ suffixENTITLEMENTS%ENTITLEMENTS%
 ├ nameNICKNAME
 ├ telecomPhone Numbers
 ├ telecomWORKPHONE
  │ └ value%WORKPHONE%
 ├ telecomALTPHONE
  │ └ value%ALTPHONE%
 ├ telecomCELLPHONE
  │ └ value%CELLPHONE%
 ├ telecomFAXPHONE
  │ └ value%FAXPHONE%
 ├ telecomPAGERPHONE
  │ └ value%PAGERPHONE%
 ├ telecomEMAIL
  │ └ value%EMAIL%
 ├ genderSEXMapCode(%SEX%,"GENDER")
 ├ birthDateDATEOFBIRTH%DATEOFBIRTH%
 ├ deceased[x]DATEOFDEATHIfNull(%DATEOFDEATH%).Then(Equals("X",%PSTATUS%)) | IfSet(%DATEOFDEATH%).Then(%DATEOFDEATH%)
 ├ addressADDRESSMakeSearchAddress(%ADDRESS1%,%ADDRESS2%,%CITY%,%STATE%,%ZIP%,%COUNTRY%)
  │ ├ lineAddress Lines
  │ ├ lineADDRESS1%ADDRESS1%
  │ ├ lineADDRESS2%ADDRESS2%
  │ ├ cityCITY%CITY%
  │ ├ stateSTATE%STATE%
  │ ├ postalCodeZIP%ZIP%
  │ └ countryCOUNTRY%COUNTRY%
 ├ maritalStatusMARITALSTATUSMapConcept(%MARITALSTATUS%,"MARITALSTATUS")
 ├ photoPHOTO_IDMakeBinary("Photo",%PHOTO_ID%)
 ├ communicationLANGCODE
  │ ├ languageMakeConcept(%LANGCODE%,"urn:ietf:bcp:47",%PREFLANG%)
  │ └ preferredtrue
 ├ careProviderPrimaryCareProviderMakeReference("USR",%PRICAREID%,"Practitioner")
 └ managingOrganizationHOMELOCATIONMakeReference("LOCREG",%HOMELOCATION%,"Organization")