resource_types/resource_types library
Classes
- AllergyIntoleranceReactionUsCore
-
AllergyIntoleranceReaction
Risk of harmful or undesirable, - AllergyIntoleranceUsCore
-
AllergyIntolerance
Risk of harmful or undesirable, physiological - BundleEntryUsCore
- BundleEntryUsCore A container for a collection of resources.
- BundleLinkUsCore
- BundleLinkUsCore A container for a collection of resources.
- BundleRequestUsCore
- BundleRequestUsCore A container for a collection of resources.
- BundleResponseUsCore
- BundleSearchUsCore
- BundleSearchUsCore A container for a collection of resources.
- BundleUsCore
- BundleUsCore A container for a collection of resources.
- CapabilityStatementDocumentUsCore
- CapabilityStatementDocumentUsCore A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
- CapabilityStatementEndpointUsCore
- CapabilityStatementEndpointUsCore A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
- CapabilityStatementImplementationUsCore
- CapabilityStatementImplementationUsCore A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
- CapabilityStatementInteraction1UsCore
- CapabilityStatementInteraction1UsCore A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
- CapabilityStatementInteractionUsCore
- CapabilityStatementInteractionUsCore A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
- CapabilityStatementMessagingUsCore
- CapabilityStatementMessagingUsCore A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
- CapabilityStatementOperationUsCore
- CapabilityStatementOperationUsCore A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
- CapabilityStatementResourceUsCore
- CapabilityStatementResourceUsCore A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
- CapabilityStatementRestUsCore
- CapabilityStatementRestUsCore A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
- CapabilityStatementSearchParamUsCore
- CapabilityStatementSearchParamUsCore A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
- CapabilityStatementSecurityUsCore
- CapabilityStatementSecurityUsCore A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
- CapabilityStatementSoftwareUsCore
- CapabilityStatementSoftwareUsCore A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
- CapabilityStatementSupportedMessageUsCore
- CapabilityStatementSupportedMessageUsCore A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
- CapabilityStatementUsCore
- CapabilityStatementUsCore A Capability Statement documents a set of
- CarePlanUsCore
- CarePlanUsCore Describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions.
- CareTeamParticipantUsCore
- CareTeamUsCore
- ConditionUsCore
- DeviceDeviceNameUsCore
- DeviceUdiCarrierUsCore
- DeviceUsCore
- DiagnosticReportUsCore
- DocumentReferenceContentUsCore
- DocumentReferenceContextUsCore
- DocumentReferenceUsCore
- EncounterHospitalizationUsCore
- EncounterLocationUsCore
- EncounterParticipantUsCore
- EncounterUsCore
- EndpointUsCore
- GoalTargetUsCore
- GoalUsCore
- ImmunizationUsCore
- LocationPositionUsCore
- LocationUsCore
- MedicationRequestDispenseRequestUsCore
- MedicationRequestInitialFillUsCore
- MedicationRequestUsCore
- MedicationUsCore
- ObservationComponentUsCore
- ObservationReferenceRangeUsCore
- ObservationUsCore
- OperationOutcomeIssueUsCore
- OperationOutcomeUsCore
- OrganizationUsCore
- PatientCommunicationUsCore
- PatientUsCore
- PractitionerQualificationUsCore
- PractitionerRoleUsCore
- PractitionerUsCore
- ProcedureFocalDeviceUsCore
- ProcedurePerformerUsCore
- ProcedureUsCore
- ProvenanceAgentUsCore
- ProvenanceUsCore
Enums
- AllergyIntoleranceClinicalStatus
- AllergyIntoleranceClinicalStatus - enum containing the most used types
- AllergyIntoleranceIdentity
- AllergyIntoleranceIdentity - enum of the most used types
- AllergyIntoleranceVerificationStatus
- AllergyIntoleranceVerificationStatus - enum of the most used types
- BodySiteForBp
- CarePlanIntent
- CarePlanStatus
- CareTeamProviderRole
- CareTeamStatus
- ConditionCategory
- ConditionClinicalStatus
- ConditionVerificationStatus
- DiagnosticReportCategory
- DiagnosticReportStatus
- DocumentReferenceType
- EncounterType
- ImmunizationStatus
- ImmunizationStatusReason
- ImmunizationVaccineCode
- MedicationRequestIntent
- MedicationRequestStatus
- ObservationDataAbsentReason
- PatientUsCoreBirthSex
- PatientUsCoreDetailedEthnicity
- PatientUsCoreDetailedRace
- PatientUsCoreEthnicity
- PatientUsCoreRace
- PractitionerRoleCode
- PractitionerRoleSpecialty
- ProcedureStatus
- ProvenanceAgentParticipantType
- SmokingStatus
Constants
Properties
-
codeableConceptFromAllergyIntoleranceClinicalStatus
→ Map<
AllergyIntoleranceClinicalStatus, CodeableConcept> -
codeableConceptFromAllergyIntoleranceClinicalStatus - enum to CodeableConcept map
final
-
codeableConceptFromAllergyIntoleranceIdentity
→ Map<
AllergyIntoleranceIdentity, CodeableConcept> -
codeableConceptAllergyIntoleranceIdentity
- enum to CodeableConcept mapfinal -
codeableConceptFromAllergyIntoleranceVerificationStatus
→ Map<
AllergyIntoleranceVerificationStatus, CodeableConcept> -
codeableConceptAllergyIntoleranceVerificationStatus
- enum to CodeableConcept mapfinal -
codeableConceptFromBodySiteForBp
→ Map<
BodySiteForBp, CodeableConcept> -
final
-
codeableConceptFromConditionCategory
→ Map<
ConditionCategory, CodeableConcept> -
final
-
codeableConceptFromConditionClinicalStatus
→ Map<
ConditionClinicalStatus, CodeableConcept> -
final
-
codeableConceptFromConditionVerificationStatus
→ Map<
ConditionVerificationStatus, CodeableConcept> -
final
-
codeableConceptFromDiagnosticReportCategory
→ Map<
DiagnosticReportCategory, CodeableConcept> -
final
-
codeableConceptFromDocumentReferenceType
→ Map<
DocumentReferenceType, CodeableConcept> -
final
-
codeableConceptFromEncounterType
→ Map<
EncounterType, CodeableConcept> -
final
-
codeableConceptFromImmunizationStatusReason
→ Map<
ImmunizationStatusReason, CodeableConcept> -
final
-
codeableConceptFromImmunizationVaccineCode
→ Map<
ImmunizationVaccineCode, CodeableConcept> -
final
-
codeableConceptFromObservationDataAbsentReason
→ Map<
ObservationDataAbsentReason, CodeableConcept> -
final
-
codeableConceptFromPractitionerRoleCode
→ Map<
PractitionerRoleCode, CodeableConcept> -
final
-
codeableConceptFromPractitionerRoleSpecialty
→ Map<
PractitionerRoleSpecialty, CodeableConcept> -
final
-
codeableConceptFromProvenanceAgentParticipantType
→ Map<
ProvenanceAgentParticipantType, CodeableConcept> -
final
-
codeableConceptFromProviderRole
→ Map<
CareTeamProviderRole, CodeableConcept> -
final
-
codeableConceptFromSmokingStatus
→ Map<
SmokingStatus, CodeableConcept> -
final
- codeconept → CodeableConcept
-
final
-
codeFromAllergyIntoleranceClinicalStatus
→ Map<
AllergyIntoleranceClinicalStatus, String> -
codeAllergyIntoleranceClinicalStatus
- enum to String mapfinal -
codeFromCareTeamStatus
→ Map<
CareTeamStatus, String> -
final
-
extensionFromBirthSex
→ Map<
PatientUsCoreBirthSex, FhirExtension> -
final
-
extensionFromDetailedEthnicity
→ Map<
PatientUsCoreDetailedEthnicity, FhirExtension> -
final
-
extensionFromDetailedRace
→ Map<
PatientUsCoreDetailedRace, FhirExtension> -
final
-
extensionFromEthnicity
→ Map<
PatientUsCoreEthnicity, FhirExtension> -
final
-
extensionFromRace
→ Map<
PatientUsCoreRace, FhirExtension> -
final
Functions
-
allergyIntoleranceRequest(
UsCoreRequestType requestType, Uri base, String id, {String? reference, Id? patientId, AllergyIntoleranceClinicalStatus? clinicalStatus, bool? getProvenanceResources, Map< String, String> ? headers, Resource? resource, Id? vid, Client? client, List<String> parameters = const <String>[], int? count, Instant? since, FhirDateTime? at}) → Future<Resource?> -
capabilityStatementRequest(
Uri base, {Map< String, String> ? headers, Client? client, List<String> parameters = const <String>[]}) → Future<Resource?> -
carePlanRequest(
UsCoreRequestType requestType, Uri base, String id, {String? reference, bool? carePlanCategory, FhirDateTime? date, Id? patientId, CarePlanStatus? carePlanStatus, bool? getProvenanceResources, Map< String, String> ? headers, Resource? resource, Id? vid, Client? client, List<String> parameters = const <String>[], int? count, Instant? since, FhirDateTime? at}) → Future<Resource?> -
careTeamRequest(
UsCoreRequestType requestType, Uri base, String id, {String? reference, Id? patientId, CareTeamStatus? careTeamStatus, bool? getProvenanceResources, Map< String, String> ? headers, Resource? resource, Id? vid, Client? client, List<String> parameters = const <String>[], int? count, Instant? since, FhirDateTime? at}) → Future<Resource?> -
codeFromEnum(
dynamic carePlanEnum) → Code -
codeFromImmunizationStatus(
ImmunizationStatus status) → Code -
conditionRequest(
UsCoreRequestType requestType, Uri base, String id, {String? reference, ConditionCategory? category, ConditionClinicalStatus? status, Id? patientId, FhirDateTime? onsetDate, CodeableConcept? conditionCode, bool? getProvenanceResources, Map< String, String> ? headers, Resource? resource, Id? vid, Client? client, List<String> parameters = const <String>[], int? count, Instant? since, FhirDateTime? at}) → Future<Resource?> -
medicationRequestEnumToCode(
dynamic medReqEnum) → Code -
procedureStatusToCode(
ProcedureStatus status) → Code