Union of http://hl7.org/fhir/us/davinci-pas/StructureDefinition/profile-encounter and http://hl7.org/fhir/us/davinci-pas/StructureDefinition/profile-encounter

This is the set of resources that conform to either of the profiles PAS Encounter (http://hl7.org/fhir/us/davinci-pas/StructureDefinition/profile-encounter) and PAS Encounter (http://hl7.org/fhir/us/davinci-pas/StructureDefinition/profile-encounter). E.g. what you have to deal with if you get resources conforming to one of them

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Encounter 0..*An interaction during which services are provided to the patient
... meta SΣ0..1MetaMetadata about the resource
.... extension 0..*ExtensionAdditional content defined by implementations
.... versionId Σ0..1idVersion specific identifier
.... lastUpdated SΣ0..1instantWhen the resource last changed
.... source Σ0..1uriIdentifies where the resource comes from
.... profile Σ0..*canonical(StructureDefinition)Profiles this resource claims to conform to
.... security Σ0..*CodingSecurity Labels applied to this resource
Binding: ?? (extensible): Security Labels from the Healthcare Privacy and Security Classification System.
.... tag Σ0..*CodingTags applied to this resource
Binding: ?? (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: ?? (preferred): A human language.
... text 0..1NarrativeText summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionExtension
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier SΣ0..*IdentifierIdentifier(s) by which this encounter is known
.... extension 0..*ExtensionAdditional content defined by implementations
.... use ?!Σ0..1codeusual | official | temp | secondary | old (If known)
Binding: ?? (required): Identifies the purpose for this identifier, if known .
.... type Σ0..1CodeableConceptDescription of identifier
Binding: ?? (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
.... system SΣ1..1uriThe namespace for the identifier value
Example General: http://www.acme.com/identifiers/patient
.... value SΣ1..1stringThe value that is unique
Example General: 123456
.... period Σ0..1PeriodTime period when id is/was valid for use
.... assigner Σ0..1Reference(Organization)Organization that issued id (may be just text)
... status ?!SΣ1..1codeplanned | arrived | triaged | in-progress | onleave | finished | cancelled +
Binding: ?? (required): Current state of the encounter.
... statusHistory 0..*BackboneElementList of past encounter statuses
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... status 1..1codeplanned | arrived | triaged | in-progress | onleave | finished | cancelled +
Binding: ?? (required): Current state of the encounter.
.... period 1..1PeriodThe time that the episode was in the specified status
... class SΣ1..1CodingClassification of patient encounter
Binding: ?? (extensible): Classification of the encounter.
... classHistory 0..*BackboneElementList of past encounter classes
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... class 1..1Codinginpatient | outpatient | ambulatory | emergency +
Binding: ?? (extensible): Classification of the encounter.
.... period 1..1PeriodThe time that the episode was in the specified class
... type SΣ1..*CodeableConceptSpecific type of encounter
Binding: ?? (required): Codes indicating the priority of this admission. These codes are listed within an X12 implementation guide (TR3) and maintained by X12. All X12 work products are copyrighted. See their website for licensing terms and conditions.
... serviceType Σ0..1CodeableConceptSpecific type of service
Binding: ?? (example): Broad categorization of the service that is to be provided.
... priority 0..1CodeableConceptIndicates the urgency of the encounter
Binding: ?? (example): Indicates the urgency of the encounter.
... subject SΣ1..1Reference(PAS Beneficiary Patient | #sd-profile-beneficiary-profile-beneficiary)The patient or group present at the encounter
... episodeOfCare Σ0..*Reference(EpisodeOfCare)Episode(s) of care that this encounter should be recorded against
... basedOn 0..*Reference(ServiceRequest)The ServiceRequest that initiated this encounter
... participant SΣ0..*BackboneElementList of participants involved in the encounter
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... type SΣ0..*CodeableConceptRole of participant in encounter
Binding: ?? (extensible): Role of participant in encounter.
.... period S0..1PeriodPeriod of time during the encounter that the participant participated
.... individual SΣ0..1Reference(US Core Practitioner Profile(7.0.0) S | US Core PractitionerRole Profile(7.0.0) | US Core RelatedPerson Profile(7.0.0))Persons involved in the encounter other than the patient
... appointment Σ0..*Reference(Appointment)The appointment that scheduled this encounter
... period S0..1PeriodThe start and end time of the encounter
... length 0..1DurationQuantity of time the encounter lasted (less time absent)
... reasonCode SΣ0..*CodeableConceptCoded reason the encounter takes place
Binding: ?? (preferred): Reason why the encounter takes place.
... reasonReference SΣ0..*Reference(US Core Condition Problems and Health Concerns Profile(7.0.0) S | US Core Condition Encounter Diagnosis Profile(7.0.0) S | US Core Procedure Profile(7.0.0) | Observation | ImmunizationRecommendation)Reason the encounter takes place (reference)
... diagnosis Σ0..*BackboneElementThe list of diagnosis relevant to this encounter
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... condition Σ1..1Reference(Condition | Procedure)The diagnosis or procedure relevant to the encounter
.... use 0..1CodeableConceptRole that this diagnosis has within the encounter (e.g. admission, billing, discharge …)
Binding: ?? (preferred): The type of diagnosis this condition represents.
.... rank 0..1positiveIntRanking of the diagnosis (for each role type)
... account 0..*Reference(Account)The set of accounts that may be used for billing for this Encounter
... hospitalization S0..1BackboneElementDetails about the admission to a healthcare service
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... preAdmissionIdentifier 0..1IdentifierPre-admission identifier
.... origin 0..1Reference(Location | Organization)The location/organization from which the patient came before admission
.... admitSource S0..1CodeableConceptFrom where patient was admitted (physician referral, transfer)
Binding: ?? (required): Codes indicating the source of this admission. These codes are listed within an X12 implementation guide (TR3) and maintained by X12. All X12 work products are copyrighted. See their website for licensing terms and conditions.
.... reAdmission 0..1CodeableConceptThe type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission
Binding: ?? (example): The reason for re-admission of this hospitalization encounter.
.... dietPreference 0..*CodeableConceptDiet preferences reported by the patient
Binding: ?? (example): Medical, cultural or ethical food preferences to help with catering requirements.
.... specialCourtesy 0..*CodeableConceptSpecial courtesies (VIP, board member)
Binding: ?? (preferred): Special courtesies.
.... specialArrangement 0..*CodeableConceptWheelchair, translator, stretcher, etc.
Binding: ?? (preferred): Special arrangements.
.... destination 0..1Reference(Location | Organization)Location/organization to which the patient is discharged
.... dischargeDisposition S0..1CodeableConceptCategory or kind of location after discharge
Binding: ?? (preferred): [National Uniform Billing Committee], manual UB-04, UB form locator 17
... location S0..*BackboneElementList of locations where the patient has been
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... location S1..1Reference(US Core Location Profile(7.0.0))Location the encounter takes place
.... status 0..1codeplanned | active | reserved | completed
Binding: ?? (required): The status of the location.
.... physicalType 0..1CodeableConceptThe physical type of the location (usually the level in the location hierachy - bed room ward etc.)
Binding: ?? (example): Physical form of the location.
.... period 0..1PeriodTime period during which the patient was present at the location
... serviceProvider S0..1Reference(US Core Organization Profile(7.0.0))The organization (facility) responsible for this encounter
... partOf 0..1Reference(Encounter)Another Encounter this encounter is part of

doco Documentation for this format