Validation Results for TWPAS

Generated Thu Dec 12 17:51:23 CST 2024, FHIR version 4.0.1 for tw.gov.mohw.nhi.pas#1.0.1 (canonical = https://twcore.mohw.gov.tw/ig/pas (history)). See Full QA Report

Quality Checks
Publisher Version:	IG Publisher Version: v1.8.1
Publication Code:	n/a . PackageId = tw.gov.mohw.nhi.pas, Canonical = https://twcore.mohw.gov.tw/ig/pas
Realm Check for n/a:	n/a
Publication Request:	package-id tw.gov.mohw.nhi.pas version 1.0.1 path https://twcore.mohw.gov.tw/ig/pas/1.0.1 Pub-Mode milestone status release Release-Label release Sequence (Group) STU1 desc 修改Profile、範例。 descmd 2024/12/11 (詳細說明請參照應用說明)： 繼承新版(v0.3.2)TW Core IG。 修改Profile: 事前審查-Bundle TWPAS 修改Profile: 事前審查-Claim TWPAS 修改Profile: 事前審查回覆-ClaimResponse TWPAS 修改Profile: 自主審查報備-ClaimResponse Self Assessment TWPAS 修改Profile: 影像報告-DiagnosticReport Image TWPAS 修改Profile: 檢查報告-DiagnosticReport TWPAS 修改Profile: 就醫科別-Encounter TWPAS 修改Profile: 基因資訊-Observation Diagnostic TWPAS 修改Profile: 放射治療-Procedure TWPAS 修改Profile: 放射治療總劑量-Substance TWPAS 修改ValueSet: LOINC-健保事前審查-基因突變類型值集 修改ValueSet: LOINC-健保事前審查-基因檢測檢體類型值集 修改ValueSet: SCT + NCI-健保事前審查-癌症分期量表項目值集 新增CodeSystem: INCa-健保事前審查-基因突變類型 修改CodeSystem: NHI-健保事前審查-醫令類別 修改CodeSystem: NHI-健保事前審查-給付適應症 修改CodeSystem: NHI-健保事前審查-補充資訊類別 新增Example Bundle: 事前審查-自主審查報備、多份影像報告（UUID）範例 Error fetching package-list from https://twcore.mohw.gov.tw/ig/pas: Not Acceptable This IG has never been published, so the version should start with '0.' or include a patch version e.g. '-ballot' This appears to be the first publication, so first must be true This IG is not yet published at all, so there must be "first" : true in the publication request No publication request category found (needed for first publication - consult FHIR product director for a value No publication request title found (needed for first publication) No publication request introduction found (needed for first publication) No publication request ci-build found (needed for first publication)
Supressed Messages:	53 Suppressed Issues
Dependency Checks:	Package Version FHIR Canonical Web Base Comment tw.gov.mohw.nhi.pas 1.0.1 R4 https://twcore.mohw.gov.tw/ig/pas hl7.terminology.r4 6.1.0 M R4 http://terminology.hl7.org http://terminology.hl7.org/6.1.0 hl7.fhir.uv.extensions.r4 5.1.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.1.0 tw.gov.mohw.twcore 0.3.2 U R4 https://twcore.mohw.gov.tw/ig/twcore https://twcore.mohw.gov.tw/ig/twcore/0.3.2 hl7.terminology.r4 6.1.0 M R4 http://terminology.hl7.org http://terminology.hl7.org/6.1.0 see above hl7.fhir.uv.extensions.r4 5.1.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.1.0 see above hl7.fhir.uv.ips 1.1.0 M R4 http://hl7.org/fhir/uv/ips http://hl7.org/fhir/uv/ips/STU1.1 hl7.terminology.r4 5.0.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/5.0.0 Latest Release is 6.1.0 fhir.dicom 2023.3.20230704 O R4 http://fhir.org/packages/fhir.dicom http://fhir.org/packages/fhir.dicom Matched to latest patch release (2022.4.20221006->2023.3.20230704). Latest Release is 2024.2.20240331 hl7.fhir.uv.sdc 3.0.0 M R4 http://hl7.org/fhir/uv/sdc http://hl7.org/fhir/uv/sdc/STU3 hl7.fhir.r4.examples 4.0.1 O R4 http://hl7.org/fhir http://hl7.org/fhir/R4 Latest Release is 5.0.0 hl7.fhir.us.davinci-pas 2.0.1 M R4 http://hl7.org/fhir/us/davinci-pas http://hl7.org/fhir/us/davinci-pas/STU2 hl7.terminology.r4 5.3.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/5.3.0 Latest Release is 6.1.0 hl7.fhir.uv.extensions.r4 1.0.0 O R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/1.0.0 Latest Release is 5.1.0 hl7.fhir.us.core 3.1.1 O R4 http://hl7.org/fhir/us/core http://hl7.org/fhir/us/core/STU3.1.1 Latest Release is 7.0.0 hl7.fhir.us.davinci-crd 2.0.0 V R4 http://hl7.org/fhir/us/davinci-crd http://hl7.org/fhir/us/davinci-crd/STU2 hl7.terminology.r4 5.3.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/5.3.0 see above. Latest Release is 6.1.0 hl7.fhir.uv.extensions.r4 1.0.0 O R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/1.0.0 see above. Latest Release is 5.1.0 hl7.fhir.us.core 3.1.1 O R4 http://hl7.org/fhir/us/core http://hl7.org/fhir/us/core/STU3.1.1 see above. Latest Release is 7.0.0 hl7.fhir.uv.sdc 3.0.0 M R4 http://hl7.org/fhir/uv/sdc http://hl7.org/fhir/uv/sdc/STU3 see above hl7.fhir.us.davinci-hrex 1.0.0 O R4 http://hl7.org/fhir/us/davinci-hrex http://hl7.org/fhir/us/davinci-hrex/STU1 Latest Release is 1.1.0 hl7.fhir.us.core 3.1.1 O R4 http://hl7.org/fhir/us/core http://hl7.org/fhir/us/core/STU3.1.1 see above. Latest Release is 7.0.0 hl7.fhir.us.udap-security 0.1.0 O R4 http://hl7.org/fhir/us/udap-security http://hl7.org/fhir/us/udap-security/2021Sep Latest Release is 1.1.0 hl7.fhir.us.core 3.1.1 O R4 http://hl7.org/fhir/us/core http://hl7.org/fhir/us/core/STU3.1.1 see above. Latest Release is 7.0.0 us.nlm.vsac 0.11.0 O R4 http://fhir.org/packages/us.nlm.vsac http://fhir.org/packages/us.nlm.vsac Latest Release is 0.21.0 hl7.fhir.uv.subscriptions-backport.r4 1.1.0 M R4 http://hl7.org/fhir/uv/subscriptions-backport http://hl7.org/fhir/uv/subscriptions-backport/STU1.1 hl7.terminology.r4 5.0.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/5.0.0 see above. Latest Release is 6.1.0 Templates: cdc-template#0.1 -> fhir.base.template#current. Tools: 0.3.0
Dependent IGs:	no references
Global Profiles:	(none declared)
Terminology Server(s):	http://tx.fhir.org/r4 (details)
HTA Analysis:	Non-HL7 Igs are exempt from terminology dependency analysis
R5 Dependencies:	(none)
Draft Dependencies:	hl7.fhir.r4.core#4.0.1: GuideParameterCode (15 uses), LOINCCodes (10 uses), CommonLanguages (35 uses), Claim (3 uses), FinancialResourceStatusCodes (4 uses), ClaimTypeCodes (3 uses), Use (3 uses), Organization (20 uses), Funds Reservation Codes (3 uses), ExampleRelatedClaimRelationshipCodes (1 uses), DeviceRequest (7 uses), MedicationRequest (27 uses), VisionPrescription (2 uses), Claim Payee Type Codes (3 uses), Practitioner (12 uses), PractitionerRole (12 uses), RelatedPerson (7 uses), ServiceRequest (11 uses), Location (6 uses), ClaimCareTeamRoleCodes (1 uses), ExampleProviderQualificationCodes (1 uses), ExceptionCodes (15 uses), MissingToothReasonCodes (15 uses), ClaimInformationCategoryCodes (14 uses), ExampleDiagnosisTypeCodes (1 uses), ExampleDiagnosisOnAdmissionCodes (1 uses), ExampleDiagnosisRelatedGroupCodes (1 uses), ExampleProcedureTypeCodes (1 uses), Device (20 uses), ClaimResponse (19 uses), ExampleRevenueCenterCodes (3 uses), BenefitCategoryCodes (3 uses), ModifierTypeCodes (9 uses), ExampleProgramReasonCodes (5 uses), ExampleServicePlaceCodes (3 uses), SurfaceCodes (3 uses), Encounter (9 uses), USCLSCodes (8 uses), ExampleClaimSubTypeCodes (2 uses), ClaimProcessingCodes (2 uses), AdjudicationValueCodes (4 uses), OralSiteCodes (2 uses), ExamplePaymentTypeCodes (2 uses), PaymentAdjustmentReasonCodes (2 uses), Form Codes (2 uses), NoteType (2 uses), CommunicationRequest (2 uses), Coverage (5 uses), Adjudication Error Codes (2 uses), CoverageTypeAndSelf-PayCodes (1 uses), SubscriberRelationshipCodes (1 uses), CoverageClassCodes (1 uses), CoverageCopayTypeCodes (1 uses), ExampleCoverageFinancialExceptionCodes (1 uses), Contract (1 uses), DiagnosticReport (4 uses), CarePlan (10 uses), ImmunizationRecommendation (10 uses), NutritionOrder (7 uses), DiagnosticReportStatus (2 uses), DiagnosticServiceSectionCodes (2 uses), CareTeam (3 uses), Specimen (6 uses), SNOMEDCTClinicalFindings (2 uses), ImagingStudy (9 uses), Media (5 uses), DocumentReferenceStatus (1 uses), CompositionStatus (1 uses), DocumentRelationshipType (1 uses), EpisodeOfCare (2 uses), EncounterStatus (2 uses), EncounterType (1 uses), ParticipantType (1 uses), Appointment (2 uses), EncounterReasonCodes (1 uses), DiagnosisRole (1 uses), Account (1 uses), AdmitSource (1 uses), Diet (1 uses), SpecialCourtesy (1 uses), SpecialArrangements (1 uses), DischargeDisposition (1 uses), EncounterLocationStatus (1 uses), LocationType (1 uses), ImagingStudyStatus (1 uses), AppointmentResponse (1 uses), Task (1 uses), Endpoint (4 uses), ProcedureReasonCodes (3 uses), DocumentReference (6 uses), Laterality (1 uses), ImagingStudySeriesPerformerFunction (1 uses), EventStatus (2 uses), MediaType (1 uses), MediaModality (1 uses), MediaCollectionView/Projection (1 uses), DeviceMetric (6 uses), medicationrequest Status (2 uses), medicationRequest Status Reason Codes (2 uses), medicationRequest Intent (2 uses), medicationRequest Category Codes (1 uses), RequestPriority (2 uses), SNOMEDCTMedicationCodes (6 uses), ProcedurePerformerRoleCodes (3 uses), Condition/Problem/DiagnosisCodes (3 uses), medicationRequest Course of Therapy Codes (2 uses), SNOMEDCTAdditionalDosageInstructions (2 uses), SNOMEDCTMedicationAsNeededReasonCodes (2 uses), SNOMEDCTAnatomicalStructureForAdministrationSiteCodes (2 uses), SNOMEDCTAdministrationMethodCodes (2 uses), DoseAndRateType (2 uses), Common UCUM units (4 uses), DetectedIssue (2 uses), MedicationAdministration (6 uses), MedicationDispense (5 uses), MedicationStatement (5 uses), Procedure (8 uses), Immunization (5 uses), ObservationCategoryCodes (5 uses), SNOMEDCTBodyStructures (7 uses), ObservationMethods (4 uses), ObservationReferenceRangeMeaningCodes (6 uses), ObservationReferenceRangeAppliesToCodes (6 uses), QuestionnaireResponse (8 uses), MolecularSequence (8 uses), OperationOutcomeCodes (1 uses), OrganizationType (2 uses), ContactEntityType (2 uses), regex (2 uses), PatientRelationshipType (1 uses), PlanDefinition (1 uses), ActivityDefinition (1 uses), Measure (1 uses), Questionnaire (1 uses), ProcedureCategoryCodes(SNOMEDCT) (1 uses), Condition (2 uses), ProcedureOutcomeCodes(SNOMEDCT) (1 uses), Composition (1 uses), ProcedureFollowUpCodes(SNOMEDCT) (1 uses), ProcedureDeviceActionCodes (1 uses), FHIRDeviceTypes (1 uses), SpecimenStatus (1 uses), FHIRSpecimenCollectionMethod (1 uses), SpecimenProcessingProcedure (1 uses), Substance (4 uses), SpecimenContainerType (1 uses), FHIRSubstanceStatus (1 uses), SubstanceCategoryCodes (1 uses), SubstanceCode (1 uses) hl7.fhir.uv.extensions.r4#5.1.0: TypeMustSupport (4 uses) hl7.fhir.uv.tools.r4#0.3.0: ResourceSortExt (133 uses) hl7.terminology.r4#6.1.0: OperationOutcomeCodes (1 uses)
Modifier Extensions:	(none)
Previous Version Comparison:	Unable to compare with previous version: Unable to find version history at https://twcore.mohw.gov.tw/ig/pas (Problem #1 with package-list.json at https://twcore.mohw.gov.tw/ig/pas: Not Acceptable)
IPA Comparison:	n/a
IPS Comparison:	n/a
Validation Flags:	On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary:	errors = 0, warn = 0, info = 0, broken links = 0

n/a Show Validation Information

Suppressed Messages (Warnings, hints, broken links)

GA代碼

• % The <script> containing the javascript 'window.dataLayer = w'... is illegal and not allowed on the HL7 cibuild - need to put the script in a .js file in a trusted template if this IG is to build on the HL7 cibuild % (1 uses)

HL7 Publisher 中的程式語法錯誤，造成所有ConceptMaps產生了版本不同的多筆Warnings，此警告訊息不影響實作與實際代碼驗證。（WARNING後方的藍色字樣(1 uses) 是指WARNING在此ConceptMap中有被使用到）

• INFORMATION: ConceptMap/nhi-loinc: ConceptMap: The concept map has too many codes to validate % (1 uses)
• INFORMATION: ConceptMap/nhi-sct-body-site: ConceptMap.group[0].target: Target Code System http://snomed.info/sct is only supported on the terminology server, so the target codes are not validated for performance reasons (1 uses)

Misleadeable UCUM codes，不影響驗證。（INFORMATION後方的 藍色字樣(1uses) 是指INFORMATION在此Profile中有被使用到）

• WARNING: Bundle/bun-1: Bundle.entry[17].resource/*MedicationRequest/medReq-treat*/.dosageInstruction[0].doseAndRate[0].dose.ofType(Quantity): UCUM Codes that contain human readable annotations like {tbl} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit 'tablets' SHOULD contain the annotation (it does not) (1 uses)
• WARNING: Bundle/bun-3: Bundle.entry[16].resource/*MedicationRequest/medReq-treat*/.dosageInstruction[0].doseAndRate[0].dose.ofType(Quantity): UCUM Codes that contain human readable annotations like {tbl} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit 'tablets' SHOULD contain the annotation (it does not) (1 uses)
• WARNING: MedicationRequest/medReq-treat: MedicationRequest.dosageInstruction[0].doseAndRate[0].dose.ofType(Quantity): UCUM Codes that contain human readable annotations like {tbl} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit 'tablets' SHOULD contain the annotation (it does not) (1 uses)

使用預設的 HL7 代碼系統，但 HL7 validator 無法辨識代碼系統，此屬於HL7 validator 程式本身問題，非IG 設計問題，此提示訊息不影響實作與實際代碼驗證。（INFORMATION後方的藍色字樣(1 uses) 是指INFORMATION在此Profile中有被使用到）

• % There are no valid display names found for the code http://loinc.org#LA9634-2 for language(s) 'zh-TW'. The display is 'Absent' the default language display% (4 uses)
• INFORMATION: Bundle/bun-1: Bundle.entry[10].resource/*Observation/obs-diagnostic-min*/.interpretation[0].coding[0].display: NO_VALID_DISPLAY_FOUND_LANG_NONE_other (0 uses)
• INFORMATION: Bundle/bun-1: Bundle.entry[13].resource/*Observation/obs-lab-min*/.interpretation[0].coding[0].display: NO_VALID_DISPLAY_FOUND_LANG_NONE_other (0 uses)
• INFORMATION: Bundle/bun-3: Bundle.entry[10].resource/*Observation/obs-diagnostic-min*/.interpretation[0].coding[0].display: NO_VALID_DISPLAY_FOUND_LANG_NONE_other (0 uses)
• INFORMATION: Bundle/bun-3: Bundle.entry[13].resource/*Observation/obs-lab-min*/.interpretation[0].coding[0].display: NO_VALID_DISPLAY_FOUND_LANG_NONE_other (0 uses)
• INFORMATION: Bundle/bun-uuid-example: Bundle.entry[10].resource/*Observation/inline-obs-diagnostic*/.interpretation[0].coding[0].display: NO_VALID_DISPLAY_FOUND_LANG_NONE_other (0 uses)
• INFORMATION: Bundle/bun-uuid-example: Bundle.entry[13].resource/*Observation/inline-obs-lab*/.interpretation[0].coding[0].display: NO_VALID_DISPLAY_FOUND_LANG_NONE_other (0 uses)
• INFORMATION: Observation/obs-diagnostic-min: Observation.interpretation[0].coding[0].display: NO_VALID_DISPLAY_FOUND_LANG_NONE_other (0 uses)
• INFORMATION: Observation/obs-lab-min: Observation.interpretation[0].coding[0].display: NO_VALID_DISPLAY_FOUND_LANG_NONE_other (0 uses)
• INFORMATION: OperationOutcome/error-example: OperationOutcome.issue[0].details: Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/operation-outcome|3.0.0 (1 uses)

使用預設的 HL7 值集，但 HL7 validator 無法辨識值集，此屬於HL7 validator 程式本身問題，非IG 設計問題，此提示訊息不影響實作與實際代碼驗證。（WARNING後方的藍色字樣(1 uses) 是指WARNING在此Profile中有被使用到）

• % UCUM Codes that contain human readable annotations like {tbl} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit SHOULD contain the annotation% (14 uses)
• % which is experimental, but this structure is not labeled as experimental% (11 uses)
• WARNING: Bundle/bun-1: Bundle.entry[6].resource/*ImagingStudy/imaStu-min*/.series[0].instance[0].sopClass: ValueSet 'http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.5.html#table_B.5-1' not found (1 uses)
• WARNING: Bundle/bun-1: Bundle.entry[6].resource/*ImagingStudy/imaStu-min*/.series[0].instance[1].sopClass: ValueSet 'http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.5.html#table_B.5-1' not found (1 uses)
• WARNING: Bundle/bun-3: Bundle.entry[6].resource/*ImagingStudy/imaStu-min*/.series[0].instance[0].sopClass: ValueSet 'http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.5.html#table_B.5-1' not found (1 uses)
• WARNING: Bundle/bun-3: Bundle.entry[6].resource/*ImagingStudy/imaStu-min*/.series[0].instance[1].sopClass: ValueSet 'http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.5.html#table_B.5-1' not found (1 uses)
• WARNING: Bundle/bun-uuid-example: Bundle.entry[7].resource/*ImagingStudy/inline-imaStu*/.series[0].instance[0].sopClass: ValueSet 'http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.5.html#table_B.5-1' not found (1 uses)
• WARNING: Bundle/bun-uuid-example: Bundle.entry[7].resource/*ImagingStudy/inline-imaStu*/.series[0].instance[1].sopClass: ValueSet 'http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.5.html#table_B.5-1' not found (1 uses)
• WARNING: ImagingStudy/imaStu-min: ImagingStudy.series[0].instance[0].sopClass: ValueSet 'http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.5.html#table_B.5-1' not found (1 uses)
• WARNING: ImagingStudy/imaStu-min: ImagingStudy.series[0].instance[1].sopClass: ValueSet 'http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.5.html#table_B.5-1' not found (1 uses)

值集中的代碼量太多，Expansion僅列出前1,000筆。（INFORMATION後方的 藍色字樣(1uses) 是指INFORMATION在此Profile中有被使用到）

• % The value set include has too many codes to validate % (4 uses)
• INFORMATION: ValueSet.where(id = 'icd-10-pcs-2014-image'): The value set expansion is too large, and only a subset has been displayed (1 uses)
• INFORMATION: ValueSet.where(id = 'icd-10-pcs-2014-radiotherapy'): The value set expansion is too large, and only a subset has been displayed (1 uses)
• INFORMATION: ValueSet.where(id = 'icd-10-pcs-2023-image'): The value set expansion is too large, and only a subset has been displayed (1 uses)
• INFORMATION: ValueSet.where(id = 'icd-10-pcs-2023-radiotherapy'): The value set expansion is too large, and only a subset has been displayed (1 uses)
• INFORMATION: ValueSet.where(id = 'nhi-organization'): The value set expansion is too large, and only a subset has been displayed (1 uses)

提醒slice的pattern寫法將於R5版本不再支援，不影響驗證。（INFORMATION後方的 藍色字樣(1uses) 是指INFORMATION在此Profile中有被使用到）

• INFORMATION: StructureDefinition/Encounter-twpas: StructureDefinition.differential.element[3].slicing.discriminator[0]: The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing) (1 uses)
• INFORMATION: StructureDefinition/Encounter-twpas: StructureDefinition.snapshot.element[36].slicing.discriminator[0]: The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing) (1 uses)
• INFORMATION: StructureDefinition/ImagingStudy-twpas: StructureDefinition.snapshot.element[34].slicing.discriminator[0]: The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing) (1 uses)
• INFORMATION: StructureDefinition/MedicationRequest-apply-twpas: StructureDefinition.snapshot.element[22].slicing.discriminator[0]: The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing) (1 uses)
• INFORMATION: StructureDefinition/MedicationRequest-treat-twpas: StructureDefinition.snapshot.element[22].slicing.discriminator[0]: The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing) (1 uses)
• INFORMATION: StructureDefinition/Observation-diagnostic-twpas: StructureDefinition.differential.element[15].slicing.discriminator[0]: The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing) (1 uses)
• INFORMATION: StructureDefinition/Observation-diagnostic-twpas: StructureDefinition.snapshot.element[63].slicing.discriminator[0]: The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing) (1 uses)
• INFORMATION: StructureDefinition/Patient-twpas: StructureDefinition.snapshot.element[97].slicing.discriminator[0]: The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing) (1 uses)

提醒slice雖有多筆，但實際只能填一筆，不影響驗證。（INFORMATION後方的 藍色字樣(1uses) 是指INFORMATION在此Profile中有被使用到）

• INFORMATION: StructureDefinition.snapshot.element[15]: The slice definition for Substance.code.coding has a maximum of 1 but the slices add up to a maximum of 2. Check that this is what is intended (1 uses)
• INFORMATION: StructureDefinition.snapshot.element[20]: The slice definition for DiagnosticReport.code.coding has a maximum of 1 but the slices add up to a maximum of 2. Check that this is what is intended (1 uses)
• INFORMATION: StructureDefinition.snapshot.element[20]: The slice definition for Procedure.code.coding has a maximum of 1 but the slices add up to a maximum of 2. Check that this is what is intended (1 uses)
• INFORMATION: StructureDefinition.snapshot.element[22]: The slice definition for MedicationRequest.medication[x]:medicationCodeableConcept.coding has a maximum of 1 but the slices add up to a maximum of 3. Check that this is what is intended (1 uses)
• INFORMATION: StructureDefinition.snapshot.element[268]: The slice definition for Claim.procedure.procedure[x].coding has a maximum of 1 but the slices add up to a maximum of 3. Check that this is what is intended (1 uses)
• INFORMATION: StructureDefinition.snapshot.element[36]: The slice definition for Encounter.serviceType.coding has a maximum of 1 but the slices add up to a maximum of 3. Check that this is what is intended (1 uses)
• INFORMATION: StructureDefinition.snapshot.element[9]: The slice definition for Practitioner.identifier has a maximum of 1 but the slices add up to a maximum of 2. Check that this is what is intended (1 uses)

此條件可能回傳多個集合，但Bundle中已限制可填次數故不影響驗證。（WARNING後方的藍色字樣(1 uses) 是指WARNING在此Profile中有被使用到）

• WARNING: StructureDefinition/Claim-twpas: StructureDefinition.snapshot.element[0].constraint[6]: supportingInfo: The left side is inherently a collection, and so the expression 'coding.code = 'examinationReport'' may fail or return false if there is more than one item in the content being evaluated (1 uses)
• WARNING: StructureDefinition/Claim-twpas: StructureDefinition.snapshot.element[0].constraint[6]: supportingInfo: The left side is inherently a collection, and so the expression 'coding.code = 'geneInfo'' may fail or return false if there is more than one item in the content being evaluated (1 uses)
• WARNING: StructureDefinition/Claim-twpas: StructureDefinition.snapshot.element[0].constraint[6]: supportingInfo: The left side is inherently a collection, and so the expression 'coding.code = 'imagingReport'' may fail or return false if there is more than one item in the content being evaluated (1 uses)

此條件可能回傳多個集合，但已限制可填次數故不影響驗證。（WARNING後方的 藍色字樣(1uses) 是指WARNING在此Profile中有被使用到）

• WARNING: StructureDefinition/DocumentReference-twpas: StructureDefinition.snapshot.element[0].constraint[5]: report-title: The left side is inherently a collection, and so the expression 'content.attachment.title = 'CAR-T多團隊會議紀錄'' may fail or return false if there is more than one item in the content being evaluated (1 uses)
• WARNING: StructureDefinition/DocumentReference-twpas: StructureDefinition.snapshot.element[0].constraint[5]: report-title: The left side is inherently a collection, and so the expression 'content.attachment.title = '免疫檢查點抑制劑治療計畫'' may fail or return false if there is more than one item in the content being evaluated (1 uses)
• WARNING: StructureDefinition/DocumentReference-twpas: StructureDefinition.snapshot.element[0].constraint[5]: report-title: The left side is inherently a collection, and so the expression 'content.attachment.title = '造血幹細胞移植計畫書'' may fail or return false if there is more than one item in the content being evaluated (1 uses)

Errors sorted by type