The jira specification file appears to be out of date with the versions, artifacts and pages currently defined in the IG. A proposed revised file to be reviewed and, if appropriate, submitted as a pull request against the XML folder in https://github.com/HL7/JIRA-Spec-Artifacts. To see the differences, perform a file compare on 'template/jira-current.xml' (a normalized view of what is in Github) and 'template/jira-new.xml' (reflects current IG content)
The link 'http://hl7.org/fhir/us/core/ValueSet/simple-language' for "http://hl7.org/fhir/us/core/ValueSet/simple-language" cannot be resolvedHTML_LINK_CHECK_FAILED
The link 'http://hl7.org/fhir/us/core/ValueSet/simple-language' for "http://hl7.org/fhir/us/core/ValueSet/simple-language" cannot be resolvedHTML_LINK_CHECK_FAILED
The link 'http://hl7.org/fhir/us/core/ValueSet/simple-language' for "http://hl7.org/fhir/us/core/ValueSet/simple-language" cannot be resolvedHTML_LINK_CHECK_FAILED
The link 'http://hl7.org/fhir/us/core/ValueSet/simple-language' for "http://hl7.org/fhir/us/core/ValueSet/simple-language" cannot be resolvedHTML_LINK_CHECK_FAILED
The link 'http://hl7.org/fhir/us/core/ValueSet/simple-language' for "http://hl7.org/fhir/us/core/ValueSet/simple-language" cannot be resolvedHTML_LINK_CHECK_FAILED
The link 'http://hl7.org/fhir/us/core/ValueSet/simple-language' for "http://hl7.org/fhir/us/core/ValueSet/simple-language" cannot be resolvedHTML_LINK_CHECK_FAILED
The link 'http://hl7.org/fhir/us/core/ValueSet/simple-language' for "http://hl7.org/fhir/us/core/ValueSet/simple-language" cannot be resolvedHTML_LINK_CHECK_FAILED
The link 'http://hl7.org/fhir/us/core/ValueSet/simple-language' for "http://hl7.org/fhir/us/core/ValueSet/simple-language" cannot be resolvedHTML_LINK_CHECK_FAILED
The link 'http://hl7.org/fhir/us/core/ValueSet/simple-language' for "http://hl7.org/fhir/us/core/ValueSet/simple-language" cannot be resolvedHTML_LINK_CHECK_FAILED
The link 'http://hl7.org/fhir/us/core/ValueSet/simple-language' for "http://hl7.org/fhir/us/core/ValueSet/simple-language" cannot be resolvedHTML_LINK_CHECK_FAILED
The link 'http://hl7.org/fhir/us/core/ValueSet/simple-language' for "http://hl7.org/fhir/us/core/ValueSet/simple-language" cannot be resolvedHTML_LINK_CHECK_FAILED
The link 'http://hl7.org/fhir/us/core/ValueSet/simple-language' for "http://hl7.org/fhir/us/core/ValueSet/simple-language" cannot be resolvedHTML_LINK_CHECK_FAILED
The link 'http://hl7.org/fhir/us/core/ValueSet/simple-language' for "http://hl7.org/fhir/us/core/ValueSet/simple-language" cannot be resolvedHTML_LINK_CHECK_FAILED
The link 'http://hl7.org/fhir/us/core/ValueSet/simple-language' for "http://hl7.org/fhir/us/core/ValueSet/simple-language" cannot be resolvedHTML_LINK_CHECK_FAILED
The link 'http://hl7.org/fhir/us/core/ValueSet/simple-language' for "http://hl7.org/fhir/us/core/ValueSet/simple-language" cannot be resolvedHTML_LINK_CHECK_FAILED
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'The patient.identifier element in this profile is available to be populated but SHALL contain only non-personally-identifiable codes, such as an account or user ID assigned during an anonymous interaction with the server. 'CONFORMANCE_STATEMENT_WORD
en/error_handling.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'In the event that the RTPBC source system (payer/PBM, discount pricing source) is unable to fully process a request because of data or business rule issue, that system SHALL respond by populating the .error composite in the ClaimResponse resource. Values SHOULD be taken from the set of RTPBC error codes as defined in the RTPBC Error Code Value Set. 'CONFORMANCE_STATEMENT_WORD
The link 'file:///C:/FHIR/IGs/carin-rtpbc-new/output/en/Bundle-rtpbc-bundle-response-price-source.html' for "RTPBC response from a pricing source" cannot be resolvedHTML_LINK_CHECK_FAILED
No definition could be found for URL value 'http://hl7.org/fhir/tools/StructureDefinition/expansion-parameters'
Editor's Comment: Receiving an error related to expansion-parameters described in this Zulip thread as caused by a publisher issue: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Publisher.20v2.2E0.2E24.20-.20error.20in.20local.20build/with/547712458Type_Specific_Checks_DT_URL_Resolve
A definition could not be found for Canonical URL 'http://hl7.org/fhir/us/core/ValueSet/simple-language'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVE
StructureDefinition.text.div
error
Hyperlink 'http://hl7.org/fhir/us/core/ValueSet/simple-language' at 'div/table/tr/td/a' for 'http://hl7.org/fhir/us/core/ValueSet/simple-language' does not resolve
The code 'AA' is not valid in the system https://www.usps.com/ (Unknown code 'AA' in the CodeSystem 'https://www.usps.com/' version 'null')VALUESET_INCLUDE_INVALID_CONCEPT_CODE
The code 'AE' is not valid in the system https://www.usps.com/ (Unknown code 'AE' in the CodeSystem 'https://www.usps.com/' version 'null')VALUESET_INCLUDE_INVALID_CONCEPT_CODE
The code 'AP' is not valid in the system https://www.usps.com/ (Unknown code 'AP' in the CodeSystem 'https://www.usps.com/' version 'null')VALUESET_INCLUDE_INVALID_CONCEPT_CODE
Wrong Display Name 'Virgin Islands' for https://www.usps.com/#VI. Valid display is 'Virgin Islands of the U.S.' (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong codeVALUESET_CODE_CONCEPT_HINT
Examples of MessageHeader resources are included in the full request and response bundle examples.
INFORMATION: StructureDefinition.where(url = 'http://hl7.org/fhir/us/carin-rtpbc/StructureDefinition/rtpbc-request-messageheader'): The Implementation Guide contains no explicitly linked examples for this profile (1 uses)
INFORMATION: StructureDefinition.where(url = 'http://hl7.org/fhir/us/carin-rtpbc/StructureDefinition/rtpbc-response-messageheader'): The Implementation Guide contains no explicitly linked examples for this profile (1 uses)
Have not yet marked conformance clauses
INFORMATION: en/error_handling.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'In the event that the RTPBC source system (payer/PBM, discount pricing source) is unable to fully process a request because of data or business rule issue, that system SHALL respond by populating the .error composite in the ClaimResponse resource. Values SHOULD be taken from the set of RTPBC error codes as defined in the RTPBC Error Code Value Set. 'cxd (0 uses)
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'In the event that the RTPBC source system (payer/PBM, discount pricing source) is unable to fully process a request because of data or business rule issue, that system SHALL respond by populating the .error composite in the ClaimResponse resource. Values SHOULD be taken from the set of RTPBC error codes as defined in the RTPBC Error Code Value Set. ' (0 uses)
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'SHALL: ' (2 uses)
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'When a party that has implemented the responder role of this implementation guide and can also respond to the provider-focused NCPDP Real-time Prescription Benefit (RTPB) transaction, it SHALL ensure that it returns consistent values for information that is common between the two standards.' (1 uses)
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Pharmacy phone and address SHOULD be populated to assist in identifying a particular pharmacy location, especially when identifying the pharmacy using an NPI' (1 uses)
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Responders SHOULD return pricing and coverage information for relevant drug/pharmacy alternatives, in the addItem composite' (1 uses)
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'The following SMART on FHIR Capability Sets SHOULD be supported when retrieving from RTPBC data sources that return patient-specific information–such as an insurer system that returns responses containing a member's benefit balances and coverage information.' (1 uses)
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'dosageInstruction SHOULD be used when determining days supply' (1 uses)
Receiving an error related to expansion-parameters described in this Zulip thread as caused by a publisher issue: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Publisher.20v2.2E0.2E24.20-.20error.20in.20local.20build/with/547712458
No definition could be found for URL value 'http://hl7.org/fhir/tools/StructureDefinition/expansion-parameters' (1 uses)
Temporarily suppressing this while we decide how to address terminology items in the STU2 IG
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG) (4 uses)
The Non-PHI Claim profile excludes personally-identifiable information. The patient.display and insuance.coverage.display elements in this profile are not used (0..0).
WARNING: Bundle/rtpbc-bundle-request-non-phi-1: Bundle.entry[1].resource/*Claim/rtpbc-claim-non-phi-1*/.insurance[0].coverage: A Reference without an actual reference or identifier should have a display (1 uses)
WARNING: Bundle/rtpbc-bundle-request-non-phi-1: Bundle.entry[1].resource/*Claim/rtpbc-claim-non-phi-1*/.patient: A Reference without an actual reference or identifier should have a display (1 uses)
WARNING: Bundle/rtpbc-bundle-request-non-phi-2: Bundle.entry[1].resource/*Claim/rtpbc-claim-non-phi-2*/.insurance[0].coverage: A Reference without an actual reference or identifier should have a display (0 uses)
WARNING: Bundle/rtpbc-bundle-request-non-phi-2: Bundle.entry[1].resource/*Claim/rtpbc-claim-non-phi-2*/.patient: A Reference without an actual reference or identifier should have a display (0 uses)
WARNING: Claim/rtpbc-claim-non-phi-1: Claim.insurance[0].coverage: A Reference without an actual reference or identifier should have a display (1 uses)
WARNING: Claim/rtpbc-claim-non-phi-1: Claim.patient: A Reference without an actual reference or identifier should have a display (1 uses)
WARNING: Claim/rtpbc-claim-non-phi-2: Claim.insurance[0].coverage: A Reference without an actual reference or identifier should have a display (0 uses)
WARNING: Claim/rtpbc-claim-non-phi-2: Claim.patient: A Reference without an actual reference or identifier should have a display (0 uses)
The Non-PHI MedicationRequest profile excludes personally-identifiable information. The subject.display element in this profile is not used (0..0).
WARNING: Bundle/rtpbc-bundle-request-non-phi-1: Bundle.entry[2].resource/*MedicationRequest/rtpbc-medicationrequest-non-phi-1*/.subject: A Reference without an actual reference or identifier should have a display (1 uses)
WARNING: Bundle/rtpbc-bundle-request-non-phi-2: Bundle.entry[2].resource/*MedicationRequest/rtpbc-medicationrequest-non-phi-2*/.subject: A Reference without an actual reference or identifier should have a display (0 uses)
WARNING: MedicationRequest/rtpbc-medicationrequest-non-phi-1: MedicationRequest.subject: A Reference without an actual reference or identifier should have a display (1 uses)
WARNING: MedicationRequest/rtpbc-medicationrequest-non-phi-2: MedicationRequest.subject: A Reference without an actual reference or identifier should have a display (1 uses)
The other identifiers in this slice, NPI an NCPDP Provider ID are both marked Must Suport and this is discussed in Must Support guidance in the IG.
The slice 'CLIA' on path 'Organization.identifier' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true (1 uses)
The slice 'NAIC' on path 'Organization.identifier' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true (1 uses)
The pattern is set in a repeating slice. The pattern is expected to hold for all repetitions of that slice. (It's fixing the 'system' for the identifier.)
The repeating element has a pattern. The pattern will apply to all the repeats (this has not been clear to all users) (3 uses)
This implementation guide uses external code systems which are listed in terminology.hl7.org (THO) but whose codes are not published by HL7
A definition for CodeSystem 'http://terminology.hl7.org/CodeSystem/NCPDPPharmacyType' could not be found, so the code cannot be validated (7 uses)
Error from https://tx.fhir.org/r4: A definition for CodeSystem 'http://canadapost.ca/CodeSystem/ProvinceCodes' could not be found, so the value set cannot be expanded (0 uses)
Error from https://tx.fhir.org/r4: A definition for CodeSystem 'http://terminology.hl7.org/CodeSystem/NCPDPPharmacyType' could not be found, so the value set cannot be expanded (0 uses)
Error from https://tx.fhir.org/r4: A definition for CodeSystem 'http://terminology.hl7.org/CodeSystem/NCPDPRejectCode' could not be found, so the value set cannot be expanded (0 uses)
The concepts in the value set include have not been validated because the terminology server https://terminologystandardsservice.ca/tx/fhir does not support batch validation (tests version < 1.7.8) (0 uses)
Unable to check whether the code is in the value set '' because the code system http://terminology.hl7.org/CodeSystem/NCPDPPharmacyType was not found (7 uses)
This warning about the deprecated maxValueSet StuctureDefinition element is inherited from the US Core Coverage profile. The US Core QA indicates the issue is recognized and may be addressed in a future update
The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.2.0 is deprecated (1 uses)
Wrong Display Name 'Virgin Islands' for https://www.usps.com/#VI. Valid display is 'Virgin Islands of the U.S.' (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
hl7.fhir.us.carin-rtpbc
hl7.fhir.uv.extensions
