Bản hướng dẫn thực thi (IG) dành cho các hệ thống thông tin Y tế tại Việt Nam
1.0.0 - CI Build

Bản hướng dẫn thực thi (IG) dành cho các hệ thống thông tin Y tế tại Việt Nam, published by Cục Công nghệ thông tin - Bộ Y tế. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7vn/vn-core-ig/ and changes regularly. See the Directory of published versions

Resource Profile: VNCoreServiceRequest

Thông tin mô tả về chỉ định dịch vụ kỹ thuật

Đường dẫn URL chính thức của Profile này:

http://fhir.ehealth.gov.vn/core/StructureDefinition/vn-core-service-request

Nội dung Profile

Thông tin bổ sung cho các thông tin hiển thị (Nội dung mô tả, Differential Table, Snapshot Table, ...).

Profile này được dựa trên Resource ServiceRequest

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. ServiceRequest 0..* ServiceRequest A request for a service to be performed
... identifier S 0..* Identifier Identifiers assigned to this order
... basedOn S 0..* Reference(CarePlan | ServiceRequest | MedicationRequest | ServiceRequest profile - VN Core R4) What request fulfills
... replaces 0..* Reference(ServiceRequest | ServiceRequest profile - VN Core R4) What request replaces
... category S 0..* VNCoreCodeableConcept Classification of service
... priority S 0..1 code routine | urgent | asap | stat
... code 1..1 VNCoreCodeableConcept What is being requested/ordered
Binding: ValueSet dành cho Mã dịch vụ kỹ thuật (preferred)
... orderDetail 0..* VNCoreCodeableConcept Additional order information
... subject 1..1 Reference(Patient Profile - VN Core R4) Individual or Entity the service is ordered for
... encounter S 0..1 Reference(Encounter Profile - VN Core R4) Encounter in which the request was created
... occurrence[x] S 0..1 dateTime, Period, Timing When service should occur
... authoredOn S 0..1 dateTime Date request signed
... requester S 0..1 Reference(Practitioner Profile - VN Core R4 | PractitionerRole | Organization | Patient | Device | RelatedPerson) Who/what is requesting service
... performerType 0..1 VNCoreCodeableConcept Performer role
... performer S 0..* Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson | Practitioner Profile - VN Core R4 | HealthcareDepartment Profile - VN Core R4) Requested performer
... locationReference 0..* Reference(Location | Location Profile - VN Core R4) Requested location
... reasonCode S 0..* VNCoreCodeableConcept Explanation/Justification for procedure or service
Binding: ValueSet dành cho Mã bệnh tật (required)
... reasonReference S 0..* Reference(Condition | Observation | DiagnosticReport | DocumentReference) Explanation/Justification for service or service
... specimen S 0..* Reference(Specimen) Procedure Samples
... bodySite S 0..* VNCoreCodeableConcept Location on Body
... patientInstruction S 0..1 string Patient or consumer-oriented instructions

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. ServiceRequest C 0..* ServiceRequest A request for a service to be performed
Constraints: prr-1
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... language 0..1 code Language of the resource content
Binding: CommonLanguages (preferred): A human language.
Additional BindingsPurpose
AllLanguages Max Binding
... text 0..1 Narrative Text 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..* Resource Contained, inline Resources
... extension 0..* Extension Additional content defined by implementations
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... identifier SΣ 0..* Identifier Identifiers assigned to this order
... instantiatesCanonical Σ 0..* canonical(ActivityDefinition | PlanDefinition) Instantiates FHIR protocol or definition
... instantiatesUri Σ 0..* uri Instantiates external protocol or definition
... basedOn SΣ 0..* Reference(CarePlan | ServiceRequest | MedicationRequest | ServiceRequest profile - VN Core R4) What request fulfills
... replaces Σ 0..* Reference(ServiceRequest | ServiceRequest profile - VN Core R4) What request replaces
... requisition SΣ 0..1 Identifier Composite Request ID
... status ?!Σ 1..1 code draft | active | on-hold | revoked | completed | entered-in-error | unknown
Binding: RequestStatus (required): The status of a service order.
... intent ?!Σ 1..1 code proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
Binding: RequestIntent (required): The kind of service request.
... category SΣ 0..* VNCoreCodeableConcept Classification of service
Binding: ServiceRequestCategoryCodes (example): Classification of the requested service.
... priority SΣ 0..1 code routine | urgent | asap | stat
Binding: RequestPriority (required): Identifies the level of importance to be assigned to actioning the request.
... doNotPerform ?!Σ 0..1 boolean True if service/procedure should not be performed
... code Σ 1..1 VNCoreCodeableConcept What is being requested/ordered
Binding: ValueSet dành cho Mã dịch vụ kỹ thuật (preferred)
... orderDetail ΣC 0..* VNCoreCodeableConcept Additional order information
Binding: ServiceRequestOrderDetailsCodes (example): Codified order entry details which are based on order context.
... quantity[x] Σ 0..1 Service amount
.... quantityQuantity Quantity
.... quantityRatio Ratio
.... quantityRange Range
... subject Σ 1..1 Reference(Patient Profile - VN Core R4) Individual or Entity the service is ordered for
... encounter SΣ 0..1 Reference(Encounter Profile - VN Core R4) Encounter in which the request was created
... occurrence[x] SΣ 0..1 When service should occur
.... occurrenceDateTime dateTime
.... occurrencePeriod Period
.... occurrenceTiming Timing
... asNeeded[x] Σ 0..1 Preconditions for service
Binding: SNOMEDCTMedicationAsNeededReasonCodes (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.
.... asNeededBoolean boolean
.... asNeededCodeableConcept CodeableConcept
... authoredOn SΣ 0..1 dateTime Date request signed
... requester SΣ 0..1 Reference(Practitioner Profile - VN Core R4 | PractitionerRole | Organization | Patient | Device | RelatedPerson) Who/what is requesting service
... performerType Σ 0..1 VNCoreCodeableConcept Performer role
Binding: ParticipantRoles (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.
... performer SΣ 0..* Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson | Practitioner Profile - VN Core R4 | HealthcareDepartment Profile - VN Core R4) Requested performer
... locationCode Σ 0..* CodeableConcept Requested location
Binding: ServiceDeliveryLocationRoleType (example): A location type where services are delivered.
... locationReference Σ 0..* Reference(Location | Location Profile - VN Core R4) Requested location
... reasonCode SΣ 0..* VNCoreCodeableConcept Explanation/Justification for procedure or service
Binding: ValueSet dành cho Mã bệnh tật (required)
... reasonReference SΣ 0..* Reference(Condition | Observation | DiagnosticReport | DocumentReference) Explanation/Justification for service or service
... insurance 0..* Reference(Coverage | ClaimResponse) Associated insurance coverage
... supportingInfo 0..* Reference(Resource) Additional clinical information
... specimen SΣ 0..* Reference(Specimen) Procedure Samples
... bodySite SΣ 0..* VNCoreCodeableConcept Location on Body
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.
... note 0..* Annotation Comments
... patientInstruction SΣ 0..1 string Patient or consumer-oriented instructions
... relevantHistory 0..* Reference(Provenance) Request provenance

doco Documentation for this format

Differential View

Profile này được dựa trên Resource ServiceRequest

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. ServiceRequest 0..* ServiceRequest A request for a service to be performed
... identifier S 0..* Identifier Identifiers assigned to this order
... basedOn S 0..* Reference(CarePlan | ServiceRequest | MedicationRequest | ServiceRequest profile - VN Core R4) What request fulfills
... replaces 0..* Reference(ServiceRequest | ServiceRequest profile - VN Core R4) What request replaces
... category S 0..* VNCoreCodeableConcept Classification of service
... priority S 0..1 code routine | urgent | asap | stat
... code 1..1 VNCoreCodeableConcept What is being requested/ordered
Binding: ValueSet dành cho Mã dịch vụ kỹ thuật (preferred)
... orderDetail 0..* VNCoreCodeableConcept Additional order information
... subject 1..1 Reference(Patient Profile - VN Core R4) Individual or Entity the service is ordered for
... encounter S 0..1 Reference(Encounter Profile - VN Core R4) Encounter in which the request was created
... occurrence[x] S 0..1 dateTime, Period, Timing When service should occur
... authoredOn S 0..1 dateTime Date request signed
... requester S 0..1 Reference(Practitioner Profile - VN Core R4 | PractitionerRole | Organization | Patient | Device | RelatedPerson) Who/what is requesting service
... performerType 0..1 VNCoreCodeableConcept Performer role
... performer S 0..* Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson | Practitioner Profile - VN Core R4 | HealthcareDepartment Profile - VN Core R4) Requested performer
... locationReference 0..* Reference(Location | Location Profile - VN Core R4) Requested location
... reasonCode S 0..* VNCoreCodeableConcept Explanation/Justification for procedure or service
Binding: ValueSet dành cho Mã bệnh tật (required)
... reasonReference S 0..* Reference(Condition | Observation | DiagnosticReport | DocumentReference) Explanation/Justification for service or service
... specimen S 0..* Reference(Specimen) Procedure Samples
... bodySite S 0..* VNCoreCodeableConcept Location on Body
... patientInstruction S 0..1 string Patient or consumer-oriented instructions

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. ServiceRequest C 0..* ServiceRequest A request for a service to be performed
Constraints: prr-1
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... language 0..1 code Language of the resource content
Binding: CommonLanguages (preferred): A human language.
Additional BindingsPurpose
AllLanguages Max Binding
... text 0..1 Narrative Text 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..* Resource Contained, inline Resources
... extension 0..* Extension Additional content defined by implementations
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... identifier SΣ 0..* Identifier Identifiers assigned to this order
... instantiatesCanonical Σ 0..* canonical(ActivityDefinition | PlanDefinition) Instantiates FHIR protocol or definition
... instantiatesUri Σ 0..* uri Instantiates external protocol or definition
... basedOn SΣ 0..* Reference(CarePlan | ServiceRequest | MedicationRequest | ServiceRequest profile - VN Core R4) What request fulfills
... replaces Σ 0..* Reference(ServiceRequest | ServiceRequest profile - VN Core R4) What request replaces
... requisition SΣ 0..1 Identifier Composite Request ID
... status ?!Σ 1..1 code draft | active | on-hold | revoked | completed | entered-in-error | unknown
Binding: RequestStatus (required): The status of a service order.
... intent ?!Σ 1..1 code proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
Binding: RequestIntent (required): The kind of service request.
... category SΣ 0..* VNCoreCodeableConcept Classification of service
Binding: ServiceRequestCategoryCodes (example): Classification of the requested service.
... priority SΣ 0..1 code routine | urgent | asap | stat
Binding: RequestPriority (required): Identifies the level of importance to be assigned to actioning the request.
... doNotPerform ?!Σ 0..1 boolean True if service/procedure should not be performed
... code Σ 1..1 VNCoreCodeableConcept What is being requested/ordered
Binding: ValueSet dành cho Mã dịch vụ kỹ thuật (preferred)
... orderDetail ΣC 0..* VNCoreCodeableConcept Additional order information
Binding: ServiceRequestOrderDetailsCodes (example): Codified order entry details which are based on order context.
... quantity[x] Σ 0..1 Service amount
.... quantityQuantity Quantity
.... quantityRatio Ratio
.... quantityRange Range
... subject Σ 1..1 Reference(Patient Profile - VN Core R4) Individual or Entity the service is ordered for
... encounter SΣ 0..1 Reference(Encounter Profile - VN Core R4) Encounter in which the request was created
... occurrence[x] SΣ 0..1 When service should occur
.... occurrenceDateTime dateTime
.... occurrencePeriod Period
.... occurrenceTiming Timing
... asNeeded[x] Σ 0..1 Preconditions for service
Binding: SNOMEDCTMedicationAsNeededReasonCodes (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.
.... asNeededBoolean boolean
.... asNeededCodeableConcept CodeableConcept
... authoredOn SΣ 0..1 dateTime Date request signed
... requester SΣ 0..1 Reference(Practitioner Profile - VN Core R4 | PractitionerRole | Organization | Patient | Device | RelatedPerson) Who/what is requesting service
... performerType Σ 0..1 VNCoreCodeableConcept Performer role
Binding: ParticipantRoles (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.
... performer SΣ 0..* Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson | Practitioner Profile - VN Core R4 | HealthcareDepartment Profile - VN Core R4) Requested performer
... locationCode Σ 0..* CodeableConcept Requested location
Binding: ServiceDeliveryLocationRoleType (example): A location type where services are delivered.
... locationReference Σ 0..* Reference(Location | Location Profile - VN Core R4) Requested location
... reasonCode SΣ 0..* VNCoreCodeableConcept Explanation/Justification for procedure or service
Binding: ValueSet dành cho Mã bệnh tật (required)
... reasonReference SΣ 0..* Reference(Condition | Observation | DiagnosticReport | DocumentReference) Explanation/Justification for service or service
... insurance 0..* Reference(Coverage | ClaimResponse) Associated insurance coverage
... supportingInfo 0..* Reference(Resource) Additional clinical information
... specimen SΣ 0..* Reference(Specimen) Procedure Samples
... bodySite SΣ 0..* VNCoreCodeableConcept Location on Body
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.
... note 0..* Annotation Comments
... patientInstruction SΣ 0..1 string Patient or consumer-oriented instructions
... relevantHistory 0..* Reference(Provenance) Request provenance

doco Documentation for this format

 

Hình thức mô tả khác: Schematron

Thông tin bổ sung

Terminology Bindings

Terminology Bindings

Path Status Usage ValueSet Version Source
ServiceRequest.language Base preferred Common Languages 📍4.0.1 FHIR Std.
ServiceRequest.status Base required RequestStatus 📍4.0.1 FHIR Std.
ServiceRequest.intent Base required RequestIntent 📍4.0.1 FHIR Std.
ServiceRequest.category Base example Service Request Category Codes 📍4.0.1 FHIR Std.
ServiceRequest.priority Base required Request priority 📍4.0.1 FHIR Std.
ServiceRequest.code Base preferred ValueSet dành cho Mã dịch vụ kỹ thuật 📦1.0.0 This IG
ServiceRequest.orderDetail Base example Service Request Order Details Codes 📍4.0.1 FHIR Std.
ServiceRequest.asNeeded[x] Base example SNOMED CT Medication As Needed Reason Codes 📍4.0.1 FHIR Std.
ServiceRequest.performerType Base example Participant Roles 📍4.0.1 FHIR Std.
ServiceRequest.locationCode Base example ServiceDeliveryLocationRoleType 📦3.0.0 THO v6.5
ServiceRequest.reasonCode Base required ValueSet dành cho Mã bệnh tật 📦1.0.0 This IG
ServiceRequest.bodySite Base example SNOMED CT Body Structures 📍4.0.1 FHIR Std.

Constraints

Constraints

Id Grade Path(s) Description Expression
dom-2 error ServiceRequest If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-3 error ServiceRequest If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4 error ServiceRequest If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5 error ServiceRequest If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
dom-6 best practice ServiceRequest A resource should have narrative for robust management text.`div`.exists()
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()
prr-1 error ServiceRequest orderDetail SHALL only be present if code is present orderDetail.empty() or code.exists()