Generated Narrative: StructureDefinition athena-charge-profile Name Flags Card. Type Description & Constraints<img src="[binary]" alt="doco" style="background-color: inherit"/> athena-charge-profile 0..* Base #xD; id SΣ 1..1 id Logical id of this artifact #xD; meta Σ 0..1 Meta Metadata about the resource #xD; pid SΣ 1..1 integer PID is internal numeric value used in the Chart module and clinical data. This will be the same as the resource id in the Patient resource. #xD; patient 0..1 Reference(Patient) Who/what is the patient of the charge #xD; reference 0..1 string Reference to the Patient #xD; display 0..1 string Patient name #xD; patientProfileId SΣ 1..1 unsignedInt Patient specific id for practice management data including financial information #xD; searchName 0..1 string Patient Name for Search #xD; ticketNumber 0..1 string The ticket number for this visit. #xD; batchName 0..1 string The batch associated to the charge file. #xD; dateOfServiceFrom 0..1 dateTime The start date of service for this procedure. #xD; dateOfServiceTo 0..1 dateTime The stop date of service for this procedure. #xD; code 0..1 string Procedure code #xD; cptCode 0..1 string CPT Code #xD; units 0..1 decimal Unit information #xD; codeQualifier 0..1 string Procedure Code Qualifier for CPT Code. This column should be linked to the MedLists table MedListsId column with a TableName of ProcedureCodeQualifier. #xD; modifier1 0..1 string MedListsId for Modifier #1 #xD; modifier2 0..1 string MedListsId for Modifier #2 #xD; modifier3 0..1 string MedListsId for Modifier #3 #xD; modifier4 0..1 string MedListsId for Modifier #4 #xD; fee 0..1 Money The charge amount for the procedure #xD; value 0..1 decimal Charge amount #xD; currency 0..1 code Currency #xD; totalFee 0..1 Money Total amount distribution #xD; value 0..1 decimal Fee multiplied by Calculated Units. #xD; currency 0..1 code Currency #xD; allowed 0..1 Money The allowed amount for this procedure. #xD; value 0..1 decimal Allowed amount for the procedure #xD; currency 0..1 code Currency #xD; totalAllowed 0..1 Money Allowed multiplied by Calculated Units. #xD; value 0..1 decimal Total allowed amount value #xD; currency 0..1 code Currency #xD; rvu 0..1 string RVU amount for this procedure's fee #xD; rvuAllowed 0..1 string The RVU allowed for the procedure's fee #xD; productCode 0..1 string Product code #xD; productCodeProcedureCodeQualifier 0..1 string Product Code Procedure Code Qualifier #xD; revenueCode 0..1 string Revenue Code #xD; procedureCodeDescription 0..1 string The description of this procedure. #xD; coPayAmount 0..1 Money The coPayAmount amount for this procedure. #xD; value 0..1 decimal The coPayAmount amount for this procedure. #xD; currency 0..1 code Currency #xD; placeOfService 0..1 string The ID of the place of service for this item. This column should be linked to the MedLists table MedListsId column with a TableName of PlaceOfServiceCodes. #xD; typeOfService 0..1 integer The ID of the type of service for this item. This column should be linked to the MedLists table MedListsId column with a TableName of TypeOfServiceCodes. #xD; authDetailNum 0..1 string The authorization number for this procedure. #xD; authDate 0..1 dateTime Authrization Date in Procedure Level #xD; referralNumber 0..1 string Referral Number in Procedure Level #xD; referralDate 0..1 dateTime The optional issue date of the authorization or referral number for the case. Only the date portion of datetime is used. #xD; doctor 0..1 Reference(Practitioner) Practitioner reference for insurance. #xD; reference 0..1 string DoctorId refering to Practitioner #xD; display 0..1 string Practitioner Name #xD; visitFacility 0..1 string Facility Information #xD; visitCompany 0..1 string Facility group for this visit #xD; visitReferringDoctor 0..1 Reference(Practitioner) Referring doctor for the visit. #xD; reference 0..1 string DoctorId refering to Practitioner #xD; display 0..1 string Practitioner Name #xD; chargeServiceFacility 0..1 string Service facility group for the visit #xD; chargeRenderingProvider 0..1 Reference(Practitioner) Rendering doctor for this visit. #xD; reference 0..1 string DoctorId refering to Practitioner #xD; display 0..1 string Practitioner Name #xD; chargeSupervisingProvider 0..1 Reference(Practitioner) Supervising doctor for this visit. #xD; reference 0..1 string DoctorId refering to Practitioner #xD; display 0..1 string Practitioner Name #xD; chargeReferringProvider 0..1 Reference(Practitioner) Referring doctor for this visit. #xD; reference 0..1 string DoctorId refering to Practitioner #xD; display 0..1 string Practitioner Name #xD; chargeOrderingProvider 0..1 Reference(Practitioner) Ordering doctor for this visit. #xD; reference 0..1 string DoctorId refering to Practitioner #xD; display 0..1 string Practitioner Name #xD; <img src="[binary]" alt="doco" style="background-color: inherit"/> Documentation for this format
The Charge describes a health insurance offering comprised of a list of covered benefits (i.e. the product), costs associated with those benefits (i.e. the plan), and additional information about the offering, such as who it is owned and administered by, a coverage area, contact information, etc..
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
Unique Id for this particular athena-charge-profile.
PID is internal numeric value used in the Chart module and clinical data. This will be the same as the resource id in the Patient resource.
Who or what the charge is about. The charge can be about a person.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
SHALL have a contained resource if a local reference is provided
reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
Type the reference refers to (e.g. "Patient")
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
Aa resource (or, for logical models, the URI of the logical model).
Logical reference, when literal reference is not known
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
Patient specific id for practice management data including financial information
Internal ID of patient used in non-clinical practice management data.
The batch associated to the charge file.
The start date of service for this procedure.
The stop date of service for this procedure.
Procedure Code Qualifier for CPT Code. This column should be linked to the MedLists table MedListsId column with a TableName of ProcedureCodeQualifier.
The sum of the charges for this electronic charge.
The amount of the currency. The value includes an implicit precision in the presentation of the value.
Currency in which the charge payment has to been done.
A code indicating the currency, taken from ISO 4217.
The RVU allowed for this procedure's fee
The coPayAmount amount for this procedure.
The coPayAmount amount for the procedure.
The ID of the place of service for this item. This column should be linked to the MedLists table MedListsId column with a TableName of PlaceOfServiceCodes.
The ID of the type of service for this item. This column should be linked to the MedLists table MedListsId column with a TableName of TypeOfServiceCodes.
The authorization number for this procedure.
The optional issue date of the authorization or referral number for the case. Only the date portion of datetime is used.
Name with which Doctor or facility is associated