fhirsmith 0.3.0

package/translations/Messages.properties

@@ -0,0 +1,1510 @@
+# Validation
+_DT_Fixed_Wrong = Value is ''{0}'' but is fixed to ''{1}'' in the profile {2}
+_has_children__and_multiple_types__in_profile_ = {0} has children ({1}) and multiple types ({2}) in profile {3}
+_has_children__for_type__in_profile__but_cant_find_type = {0} has children ({1}) for type {2} in profile {3}, but can''t find type
+_has_no_children__and_no_types_in_profile_ = {0} has no children ({1}) and no types in profile {2}
+ABSTRACT_CODE_NOT_ALLOWED = Code ''{0}#{1}'' is abstract, and not allowed in this context
+Adding_wrong_path = Adding wrong path
+Adding_wrong_path__outcomegetPath___resultPathBase__ = Adding wrong path - outcome.getPath() = {0}, resultPathBase = {1}
+Adding_wrong_path_in_profile___vs_ = Adding wrong path in profile {0}: {1} vs {2}
+All_observations_should_have_a_performer = Best Practice Recommendation: In general, all observations should have a performer
+All_observations_should_have_a_subject = Best Practice Recommendation: In general, all observations should have a subject
+All_observations_should_have_an_effectiveDateTime_or_an_effectivePeriod = Best Practice Recommendation: In general, all observations should have an effective[x] ({0})
+ALL_OK = All OK
+ARRAY_CANNOT_BE_EMPTY = Array cannot be empty - the property should not be present if it has no values
+Attempt_to_a_slice_an_element_that_does_not_repeat__from__in_ = Attempt to a slice an element that does not repeat: {0}/{1} from {2} in {3}, at element {4} (slice = {5})
+ATTEMPT_TO_CHANGE_SLICING = The element at {0} defines the slicing {1} but then an element in the slicing {2} tries to redefine the slicing to {3}
+Attempt_to_replace_element_name_for_a_nonchoice_type=Attempt to replace element name for a non-choice type
+Attempt_to_use_a_snapshot_on_profile__as__before_it_is_generated = Attempt to use a snapshot on profile ''{0}'' as {1} before it is generated
+Attempt_to_use_Terminology_server_when_no_Terminology_server_is_available = Attempt to use Terminology server when no Terminology server is available
+Bad_file_path_error = ** Error: The file name you passed in, ''{0}'', doesn''t exist on the local filesystem. Please verify that this is valid file location **
+Base__Derived_profiles_have_different_types____vs___ = Base & Derived profiles have different types ({0} = {1} vs {2} = {3})
+Base_profile__has_no_type = Base profile {0} has no type
+BINDING_ADDITIONAL_D = {0} specified in an additional binding
+BINDING_ADDITIONAL_UC = {0} specified in an additional binding which applies because {1}
+BINDING_ADDITIONAL_USAGE = {0} = {1}
+BINDING_MAX = {0} specified in the max binding
+Bundle_BUNDLE_Entry_Canonical = The canonical URL ({0}) cannot match the fullUrl ({1}) unless on the canonical server itself
+Bundle_BUNDLE_Entry_Document = The first entry in a document must be a composition
+BUNDLE_BUNDLE_ENTRY_FOUND_MULTIPLE = Found {0} matches for ''{1}'' in the bundle ({2})
+BUNDLE_BUNDLE_ENTRY_FOUND_MULTIPLE_FRAGMENT = Found {0} matches for fragment {2} in resource ''{1}'' in the bundle ({3})
+BUNDLE_BUNDLE_ENTRY_FULLURL_REQUIRED = Except for transactions and batches, each entry in a Bundle must have a fullUrl which is the identity of the resource in the entry
+Bundle_BUNDLE_Entry_IdUrlMismatch = Resource ID does not match the ID in the entry fullUrl (''{0}'' vs ''{1}'')
+Bundle_BUNDLE_Entry_MismatchIdUrl = The canonical URL ({0}) cannot match the fullUrl ({1}) unless the resource id ({2}) also matches
+BUNDLE_BUNDLE_ENTRY_MULTIPLE_PROFILES_MULTIPLE_MATCHES = The {1} resource matched more than one of the allowed profiles ({3})
+BUNDLE_BUNDLE_ENTRY_MULTIPLE_PROFILES_NO_MATCH = The {1} resource did not match any of the allowed profiles (Type {2}: {3})
+BUNDLE_BUNDLE_ENTRY_MULTIPLE_PROFILES_NO_MATCH_REASON = The {1} resource did not match the profile {2} because: {3}
+Bundle_BUNDLE_Entry_NO_LOGICAL_EXPL = Specified logical model {1} not found for resource ''Binary/{0}''
+Bundle_BUNDLE_Entry_NoFirst = Documents or Messages must contain at least one entry
+Bundle_BUNDLE_Entry_NoFirstResource = No resource on first entry
+Bundle_BUNDLE_Entry_NoFullUrl = Bundle entry missing fullUrl
+Bundle_BUNDLE_Entry_NoProfile_EXPL = Specified profile {2} not found for {0} resource of type ''{0}''
+Bundle_BUNDLE_Entry_NoProfile_TYPE = No profile found for {0} resource of type ''{1}''
+Bundle_BUNDLE_Entry_NotFound = Can''t find ''{0}'' in the bundle ({1})
+BUNDLE_BUNDLE_ENTRY_NOTFOUND_APPARENT_one = Can''t find ''{1}'' in the bundle ({2}). Note that there is a resource in the bundle with the same type and id, but it does not match because of the fullUrl based rules around matching relative references (must be ''{3}'', but found ''{4}'') 
+BUNDLE_BUNDLE_ENTRY_NOTFOUND_APPARENT_other = Can''t find ''{1}'' in the bundle ({2}). Note that there are {0} resources in the bundle with the same type and id, but they do not match because of the fullUrl based rules around matching relative references (must be ''{3}'', but found these: {4}) 
+BUNDLE_BUNDLE_ENTRY_NOTFOUND_CANNOT_one = Can''t find ''{1}'' in the bundle ({2}). Note that there is a resource in the bundle with the same type and id, but it does not match because of the fullUrl based rules around matching relative references. Found ''{3}'', but it doesn''t match because of the source fullUrl ''{4}'' 
+BUNDLE_BUNDLE_ENTRY_NOTFOUND_CANNOT_other = Can''t find ''{1}'' in the bundle ({2}). Note that there are {0} resources in the bundle with the same type and id, but they do not match because of the fullUrl based rules around matching relative references. Found ''{3}'', but none of them match because of the source fullUrl ''{4}'' 
+BUNDLE_BUNDLE_ENTRY_NOTFOUND_FRAGMENT = Can''t find ''{0}'' in the bundle ({1})
+Bundle_BUNDLE_Entry_Orphan_DOCUMENT = Entry {0} isn''t reachable by traversing links (forward or backward) from the Composition
+Bundle_BUNDLE_Entry_Orphan_MESSAGE = Entry {0} isn''t reachable by traversing links (forward or backward) from the MessageHeader, so its presence should be reviewed (is it needed to process the message?)
+BUNDLE_BUNDLE_ENTRY_REVERSE_MSG = Entry {0} isn''t reachable by traversing forwards from the MessageHeader. Check that this is meant to be included (needed to process the message)
+BUNDLE_BUNDLE_ENTRY_REVERSE_R4 = Entry {0} isn''t reachable by traversing forwards from the Composition. Only Provenance is approved to be used this way (R4 section 3.3.1)
+BUNDLE_BUNDLE_ENTRY_REVERSE_R5 = Entry {0} isn''t reachable by traversing forwards from the Composition. Check whether this should be linked directly from the composition if it''s a source of narrative content
+Bundle_BUNDLE_Entry_Type = The type ''{0}'' is not valid - no resources allowed here (allowed = {1})
+Bundle_BUNDLE_Entry_Type2 = The type ''{0}'' is not valid - must be {1} (allowed = {2})
+Bundle_BUNDLE_Entry_Type3_one = The type ''{1}'' is not valid - must be of type {2}
+Bundle_BUNDLE_Entry_Type3_other = The type ''{1}'' is not valid - must be one of {0} types: {2}
+Bundle_BUNDLE_FullUrl_Missing = Relative Reference appears inside Bundle whose entry is missing a fullUrl
+Bundle_BUNDLE_FullUrl_NeedVersion = Entries matching fullURL {0} should declare meta/versionId because there are version-specific references
+Bundle_BUNDLE_MultipleMatches = Multiple matches in bundle for reference {0}
+Bundle_BUNDLE_Not_Local = URN reference is not locally contained within the bundle {0}
+BUNDLE_BUNDLE_POSSIBLE_MATCH_NO_FU = Entry {0} matches the reference {1} by type and id but it does not match the full target URL {2} by Bundle resolution rules
+BUNDLE_BUNDLE_POSSIBLE_MATCH_WRONG_FU = Entry {0} matches the reference {1} by type and id but its fullUrl {2} does not match the full target URL {3} by Bundle resolution rules
+Bundle_Document_Date_Missing = A document must have a date (Bundle.timestamp)
+Bundle_Document_Date_Missing_html = [(type = ''document'') implies (meta.lastUpdated.hasValue())]
+BUNDLE_ENTRY_URL_ABSOLUTE = The fullUrl must be an absolute URL (not ''{0}'')
+BUNDLE_ENTRY_URL_MATCHES_NO_ID = The fullUrl ''{0}'' looks like a RESTful server URL, but the resource has no id
+BUNDLE_ENTRY_URL_MATCHES_TYPE_ID = The fullUrl ''{0}'' looks like a RESTful server URL, so it must end with the correct type and id (/{1}/{2})
+BUNDLE_LINK_SEARCH_NO_DUPLICATES = The link relationship type ''{0}'' can only occur once
+BUNDLE_LINK_SEARCH_PROHIBITED = The link relationship type ''{0}'' used in search sets is prohibited in this context
+BUNDLE_LINK_STYELSHEET_EXTERNAL = External Stylesheets other than https://hl7.org/fhir/fhir.css SHOULD not be used
+BUNDLE_LINK_STYELSHEET_INSECURE = The stylesheet reference is not secure
+BUNDLE_LINK_STYELSHEET_LINKABLE = The stylesheet reference is not a resolvable link
+BUNDLE_LINK_STYELSHEET_NOT_FOUND = The stylesheet reference could not be resolved in this bundle
+BUNDLE_LINK_UNKNOWN = The link relationship type ''{0}'' is unknown and not allowed in this context
+Bundle_MSG_Event_Count = Expected {0} but found {1} event elements
+BUNDLE_POSSSIBLE_MATCHES = The bundle contains no match for {1} by the rules of Bundle reference resolution, but it has multiple resources that match {0} by resource type and id
+BUNDLE_RULE_INVALID_INDEX = Bundle Rules index is invalid ({0})
+BUNDLE_RULE_NONE = No Rule
+BUNDLE_RULE_PROFILE_UNKNOWN = Bundle Rules profile {1} is unknown for {0}
+BUNDLE_RULE_UNKNOWN = Bundle Rule refers to invalid resource {0}
+BUNDLE_SEARCH_ENTRY_NO_RESOURCE = SearchSet Bundle Entries must have resources
+BUNDLE_SEARCH_ENTRY_NO_RESOURCE_ID = Search results must have ids
+BUNDLE_SEARCH_ENTRY_TYPE_NOT_SURE = Unable to determine if this resource is a valid resource type for this search
+BUNDLE_SEARCH_ENTRY_WRONG_RESOURCE_TYPE_MODE = This is not a matching resource type for the specified search ({0} expecting {1})
+BUNDLE_SEARCH_ENTRY_WRONG_RESOURCE_TYPE_NO_MODE = This is not a matching resource type for the specified search (is a search mode needed?) ({0} expecting {1})
+BUNDLE_SEARCH_ENTRY_WRONG_RESOURCE_TYPE_OUTCOME = This is not an OperationOutcome ({0})
+BUNDLE_SEARCH_NO_MODE = SearchSet bundles should have search modes on the entries
+BUNDLE_SEARCH_NOSELF = SearchSet Bundles should have a self link that specifies what the search was
+BUNDLE_SEARCH_SELF_NOT_UNDERSTOOD = No types could be determined from the search string, so the types can''t be checked
+Can_only_specify_profile_in_the_context = Can only specify profile in the context
+CANONICAL_MULTIPLE_VERSIONS_KNOWN = The version {2} for the {0} {1} is not known. These versions are known: {3}
+Cant_have_children_on_an_element_with_a_polymorphic_type__you_must_slice_and_constrain_the_types_first_sortElements_ = Can''t have children on an element with a polymorphic type - you must slice and constrain the types first (sortElements: {0}:{1})
+CapabalityStatement_CS_SP_WrongType = Type mismatch - SearchParameter ''{0}'' type is {1}, but type here is {2}
+CDA_UNKNOWN_TEMPLATE = The CDA Template {0} is not known
+CDA_UNKNOWN_TEMPLATE_EXT = The CDA Template {0} / {1} is not known
+CDATA_is_not_allowed = CDATA is not allowed
+Circular_snapshot_references_detected_cannot_generate_snapshot_stack__ = Circular snapshot references detected; cannot generate snapshot (stack = {0})
+CODE_CASE_DIFFERENCE = The code ''{0}'' differs from the correct code ''{1}'' by case. Although the code system ''{2}'' is case insensitive, implementers are strongly encouraged to use the correct case anyway
+Code_found_in_expansion_however_ = Code found in expansion, however: {0}
+CODESYSTEM_CONCEPT_NO_DEFINITION = HL7 Defined CodeSystems should ensure that every concept has a definition
+CODESYSTEM_CONCEPT_NO_DISPLAY = HL7 Defined CodeSystems should ensure that every concept has a display
+CODESYSTEM_CS_COMPLETE_AND_EMPTY = When a CodeSystem has content = ''complete'', it doesn't make sense for there to be no concepts defined
+CODESYSTEM_CS_COUNT_COMPLETE_WRONG = The code system is complete, but the number of concepts ({0}) does not match the stated total number ({1})
+CODESYSTEM_CS_COUNT_FRAGMENT_WRONG = The code system is a fragment/example, but the number of concepts ({0}) exceeds or matches the stated total number ({1})
+CODESYSTEM_CS_COUNT_NO_CONTENT_ALLOWED = The code system says it has no content present, but concepts are found
+CODESYSTEM_CS_COUNT_NOTPRESENT_ZERO = The code system has no content, but the exceeds the stated total number is 0 concepts - check that this isn''t a complete code system that has no concepts, or update/remove the stated count 
+CODESYSTEM_CS_COUNT_SUPPLEMENT_WRONG = The code system supplement states the total number of concepts as {1}, but this is different to the underlying code system that states a value of {0}
+CODESYSTEM_CS_HL7_MISSING_ELEMENT_SHALL = HL7 Defined CodeSystems SHALL have a stated value for the {0} element so that users know the status and meaning of the code system clearly
+CODESYSTEM_CS_HL7_MISSING_ELEMENT_SHOULD = HL7 Defined CodeSystems SHOULD have a stated value for the {0} element so that users know the status and meaning of the code system clearly
+CODESYSTEM_CS_HL7_PRESENT_ELEMENT_SUPPL = CodeSystems SHOULD NOT have a stated value for the {0} element when they are a supplement
+CODESYSTEM_CS_HL7_PRESENT_ELEMENT_SUPPL_MISSING = CodeSystem Supplements with a content value of ''supplement'' SHALL have a supplements element that specifies which code system is being supplemented
+CODESYSTEM_CS_HL7_PRESENT_ELEMENT_SUPPL_WRONG = CodeSystem Supplements SHALL have a content value of ''supplement''
+CODESYSTEM_CS_NO_SUPPLEMENT = CodeSystem {0} is a supplement, so can''t be used as a value in Coding.system
+CODESYSTEM_CS_NO_VS_NOTCOMPLETE = Review the All Codes Value Set - incomplete CodeSystems generally should not have an all codes value set specified
+CODESYSTEM_CS_NO_VS_SUPPLEMENT1 = CodeSystems supplements should not have an all codes value set specified, and if they do, it must match the base code system
+CODESYSTEM_CS_NO_VS_SUPPLEMENT2 = CodeSystems supplements should not have an all codes value set specified, and if they do, it must match the base code system, and this one does not (''{0}'')
+CODESYSTEM_CS_NONHL7_MISSING_ELEMENT = CodeSystems SHOULD have a stated value for the {0} element so that users know the status and meaning of the code system clearly
+CODESYSTEM_CS_SUPP_CANT_CHECK = CodeSystem {0} cannot be found, so can''t check if concepts are valid
+CODESYSTEM_CS_SUPP_HIERARCHY_MEANING = The supplement declares a hierarchyMeaning of ''{0}'' that doesn''t match that in the base code system ''{1}''
+CODESYSTEM_CS_SUPP_INVALID_CODE = The code ''{1}'' is not declared in the base CodeSystem {0} so is not valid in the supplement
+CODESYSTEM_CS_SUPP_NO_SUPP = The code system is marked as a supplement, but it does not define what code system it supplements
+CODESYSTEM_CS_UNK_EXPANSION = The code provided ({2}) is not in the expansion in the value set {0}, and a code is required from this value set. The system {1} could not be found.
+CODESYSTEM_CS_VS_EXP_MISMATCH = CodeSystem {0} has an ''all system'' value set of {1}, but it is an expansion with the wrong number of concepts (found {2}, expected {3})
+CodeSystem_CS_VS_IncludeDetails = CodeSystem {0} has an ''all system'' value set of {1}, but the include has extra details
+CodeSystem_CS_VS_Invalid = CodeSystem {0} has an ''all system'' value set of {1}, but the value set doesn''t have a single include
+CodeSystem_CS_VS_WrongSystem = CodeSystem {0} has an ''all system'' value set of {1}, but the value set doesn''t have a matching system ({2})
+CODESYSTEM_DESIGNATION_DISP_CLASH_LANG = The designation ''{0}'' has no use and is in the same language (''{2}''), so is not differentiated from the base display (''{1}'')
+CODESYSTEM_DESIGNATION_DISP_CLASH_NO_LANG = The designation ''{0}'' has no use and no language, so is not differentiated from the base display (''{1}'')
+CODESYSTEM_DUPLICATE_CODE = The code ''{0}'' has already been defined
+CODESYSTEM_NOT_CONTAINED = CodeSystems are referred to directly from Coding.system, so it''s generally best for them not to be contained resources
+CODESYSTEM_PROPERTY_ABSOLUTE_URI = A property URI must be an absolute URI, but ''{0}'' is not
+CODESYSTEM_PROPERTY_BAD_HL7_URI = Unknown CodeSystem Property ''{0}''. If you are creating your own property, do not create it in the HL7 namespace
+CODESYSTEM_PROPERTY_BAD_INTERNAL_REFERENCE = The code ''{0}'' is not a valid code in this code system
+CODESYSTEM_PROPERTY_BAD_PROPERTY_CODE =  The code ''{0}'' is not a valid code in the value set ''{1}''
+CODESYSTEM_PROPERTY_CODE_DEFAULT_WARNING = The type of property ''{0}'' is ''code'', but no ValueSet information was found, so the codes will be validated as internal codes
+CODESYSTEM_PROPERTY_CODE_TYPE_MISMATCH = Wrong type ''{2}'': The code ''{0}'' identifies a property that has the type ''{1}''
+CODESYSTEM_PROPERTY_CODE_WARNING = If the type is ''code'', then the valueSet property should be provided to clarify what kind of code will be found in the element
+CODESYSTEM_PROPERTY_DUPLICATE_CODE = A property is already defined with the code ''{0}''
+CODESYSTEM_PROPERTY_DUPLICATE_URI = A property is already defined with the URI ''{0}''
+CODESYSTEM_PROPERTY_KNOWN_CODE_SUGGESTIVE = This property has only the standard code (''{0}'') but not the standard URI ''{1}'', so it has no clearly defined meaning in the terminology ecosystem
+CODESYSTEM_PROPERTY_NO_VALUE = The property ''{0}'' has no value, and cannot be understood
+CODESYSTEM_PROPERTY_SYNONYM_CHECK = The synonym ''{0}'' is not also defined in the code system. The Synonym property should only used to declare equivalence to other existing codes
+CODESYSTEM_PROPERTY_UNDEFINED = The property ''{0}'' has no definition in CodeSystem.property. Many terminology tools won''t know what to do with it
+CODESYSTEM_PROPERTY_UNKNOWN_CODE = This property has only a code (''{0}'') and not a URI, so it has no clearly defined meaning in the terminology ecosystem
+CODESYSTEM_PROPERTY_URI_CODE_MISMATCH = The URI ''{0}'' is normally assigned the code ''{1}''. Using the code ''{2}'' will usually create confusion in ValueSet filters etc
+CODESYSTEM_PROPERTY_URI_INVALID = The uri ''{3}'' for the property ''{4}'' implies a property with that URI exists in the CodeSystem {2} for {1}, or the code ''{0}'' does, but neither were found
+CODESYSTEM_PROPERTY_URI_TYPE_MISMATCH = Wrong type ''{2}'': The URI ''{0}'' identifies a property that has the type ''{1}''
+CODESYSTEM_PROPERTY_URI_UNKNOWN = The property uri ''{0}'' is not known, so the property values can not be validated fully
+CODESYSTEM_PROPERTY_URI_UNKNOWN_BASE = The base property uri ''{0}'' is not known for the property ''{1}'', so the property values can not be validated fully
+CODESYSTEM_PROPERTY_URI_UNKNOWN_TYPE = The property uri ''{0}'' is not known, so the property values can not be validated fully; unless specified elsewhere, codes will be treated as internal references
+CODESYSTEM_PROPERTY_VALUESET_NOT_FOUND = The ValueSet {0} is unknown, so the property codes cannot be validated
+CODESYSTEM_PROPERTY_WRONG_TYPE = The property ''{0}'' has the invalid type ''{1}'', when it is defined to have the type ''{2}''
+CODESYSTEM_SHAREABLE_EXTRA_MISSING = Published code systems SHOULD conform to the ShareableCodeSystem profile, which says that the element CodeSystem.{0} should be present, but it is not
+CODESYSTEM_SHAREABLE_EXTRA_MISSING_HL7 = Code systems published by HL7 SHALL conform to the ShareableCodeSystem profile, which says that the element CodeSystem.{0} should be present, but it is not
+CODESYSTEM_SHAREABLE_MISSING = Published code systems SHOULD conform to the ShareableCodeSystem profile, which says that the element CodeSystem.{0} is mandatory, but it is not present
+CODESYSTEM_SHAREABLE_MISSING_HL7 = Code systems published by HL7 SHALL conform to the ShareableCodeSystem profile, which says that the element CodeSystem.{0} is mandatory, but it is not present
+CODESYSTEM_SUPP_NO_DISPLAY = This display (''{0}'') differs from that defined by the base code system (''{1}''). Both displays claim to be the ''primary designation'' for the same language (''{2}''), and the correct interpretation of this is undefined
+CODESYSTEM_THO_CHECK = 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)
+CODESYSTEM_TOO_COSTLY_TIME = The operation ''{1}'' took too long to process (>{0}sec) (at {2})
+Coding_has_no_system__cannot_validate = Coding has no system. A code with no system has no defined meaning, and it cannot be validated. A system should be provided
+CONCEPTMAP_GROUP_SOURCE_CODE_INVALID = The source code ''{0}'' is not valid in the code system {1}
+CONCEPTMAP_GROUP_SOURCE_CODE_INVALID_VS = The source code ''{0}'' is not valid in the value set {1}
+CONCEPTMAP_GROUP_SOURCE_DISPLAY_INVALID = The source display ''{0}'' for the code ''{2}'' is not valid. Possible displays: {1}
+CONCEPTMAP_GROUP_SOURCE_INCOMPLETE = Source Code System {0} doesn''t have all content (content = {1}), so the source codes cannot be checked
+CONCEPTMAP_GROUP_SOURCE_MISSING = No Source Code System, so the source codes cannot be checked
+CONCEPTMAP_GROUP_SOURCE_SERVER_SIDE = Source Code System {0} is only supported on the terminology server, so the source codes are not validated for performance reasons
+CONCEPTMAP_GROUP_SOURCE_UNKNOWN = The Source Code System {0} is not fully defined and populated, and no sourceScope is specified, so the source code checking will not be performed 
+CONCEPTMAP_GROUP_TARGET_CODE_INVALID = The target code ''{0}'' is not valid in the code system {1}
+CONCEPTMAP_GROUP_TARGET_CODE_INVALID_VS = The target code ''{0}'' is not valid in the value set {1}
+CONCEPTMAP_GROUP_TARGET_DISPLAY_INVALID = The target display ''{0}'' for the code ''{2}'' is not valid. Possible displays: {1}
+CONCEPTMAP_GROUP_TARGET_INCOMPLETE = Target Code System {0} doesn''t have all content (content = {1}), so the target codes cannot be checked
+CONCEPTMAP_GROUP_TARGET_MISSING = No Target Code System, so the target codes cannot be checked
+CONCEPTMAP_GROUP_TARGET_PROPERTY_CODE_INVALID = The code {0} is invalid in the system {1}
+CONCEPTMAP_GROUP_TARGET_PROPERTY_INVALID = The property code ''{0}'' is not known
+CONCEPTMAP_GROUP_TARGET_PROPERTY_TYPE_MISMATCH = The type of this property should be {1} not {0}
+CONCEPTMAP_GROUP_TARGET_PROPERTY_TYPE_NO_SYSTEM = Since no system has been provided, a plain code cannot be used
+CONCEPTMAP_GROUP_TARGET_PROPERTY_TYPE_UNKNOWN_SYSTEM = The code system {0} could not be found, so code values can''t be checked
+CONCEPTMAP_GROUP_TARGET_SERVER_SIDE = Target Code System {0} is only supported on the terminology server, so the target codes are not validated for performance reasons
+CONCEPTMAP_GROUP_TARGET_UNKNOWN = The Target Code System {0} is not fully defined and populated, and no targetScope is specified, so the target code checking will not be performed
+CONCEPTMAP_SHAREABLE_EXTRA_MISSING = Published concept maps SHOULD conform to the ShareableConceptMap profile, which says that the element ConceptMap.{0} should be present, but it is not
+CONCEPTMAP_SHAREABLE_EXTRA_MISSING_HL7 = Concept maps published by HL7 SHALL conform to the ShareableConceptMap profile, which says that the element ConceptMap.{0} should be present, but it is not
+CONCEPTMAP_SHAREABLE_MISSING = Published concept maps SHOULD conform to the ShareableConceptMap profile, which says that the element ConceptMap.{0} is mandatory, but it is not present
+CONCEPTMAP_SHAREABLE_MISSING_HL7 = Concept maps published by HL7 SHALL conform to the ShareableConceptMap profile, which says that the element ConceptMap.{0} is mandatory, but it is not present
+CONCEPTMAP_VS_CONCEPT_CODE_UNKNOWN_SYSTEM = The code ''{1}'' comes from the system {0} which could not be found, so it''s not known whether it''s valid in the value set ''{2}''
+CONCEPTMAP_VS_CONCEPT_CODE_UNKNOWN_SYSTEM_VERSION = The code ''{1}'' comes from the system {0} version {3} which could not be found, so it''s not known whether it''s valid in the value set ''{2}''
+CONCEPTMAP_VS_INVALID_CONCEPT_CODE = The code ''{1}'' in the system {0} is not valid in the value set ''{2}''
+CONCEPTMAP_VS_INVALID_CONCEPT_CODE_VER = The code ''{2}'' in the system {0} version {1} is not valid in the value set ''{3}''
+CONCEPTMAP_VS_NOT_A_VS = Reference must be to a ValueSet, but found a {0} instead
+CONCEPTMAP_VS_TOO_MANY_CODES = The concept map has too many codes to validate ({0})
+CONTAINED_ORPHAN_DOM3 = The contained resource ''{0}'' is not referenced to from elsewhere in the containing resource nor does it refer to the containing resource (dom-3)
+Contained_resource_does_not_appear_to_be_a_FHIR_resource_unknown_name_ = Contained resource does not appear to be a FHIR resource (unknown name ''{0}'')
+Could_not_match_discriminator_for_slice_in_profile_one = Could not match discriminator ({1}) for slice {2} in profile {3} - the discriminator {4} does not have fixed value, binding or existence assertions
+Could_not_match_discriminator_for_slice_in_profile_other = Could not match any of the {0} discriminators for slice {2} in profile {3} - None of the {1} discriminators {4} have fixed value, binding or existence assertions
+CS_SCT_IPS_NOT_IPS = The Snomed CT code {0} ({1}) is not a member of the IPS free set
+defined_in_the_profile = Defined in the profile
+Delimited_versions_have_exact_match_for_delimiter____vs_ = Delimited versions have exact match for delimiter ''{0}'' : {1} vs {2}
+Derived_profile__has_no_derivation_value_and_so_cant_be_processed = Derived profile {0} has no derivation value and so can''t be processed
+Derived_profile__has_no_type = Derived profile {0} has no type
+Details_for__matching_against_Profile_ = Details for {0} matching against profile {1}
+Did_not_find_single_slice_ = Did not find single slice: {0}
+Did_not_find_type_root_ = Did not find type root: {0}
+Differential_does_not_have_a_slice__b_of_____in_profile_ = Differential in profile {5} does not have a slice at {6} (on {0}, position {1} of {2} / {3} / {4})
+Differential_walks_into____but_the_base_does_not_and_there_is_not_a_single_fixed_type_The_type_is__This_is_not_handled_yet = Differential walks into ''{0} (@ {1})'', but the base does not, and there is not a single fixed type. The type is {2}. This is not handled yet
+Discriminator__is_based_on_element_existence_but_slice__neither_sets_min1_or_max0 = Discriminator ({0}) is based on element existence, but slice {1} neither sets min>=1 or max=0
+Discriminator__is_based_on_type_but_slice__in__has_no_types = Discriminator ({0}) is based on type, but slice {1} in {2} has no types
+DISCRIMINATOR_BAD_PATH = Error processing path expression for discriminator: {0} (src = ''{1}'')
+Display_Name_for__should_be_one_of__instead_of_one = Wrong Display Name ''{4}'' for {1}#{2}. Valid display is {3} (for the language(s) ''{5}'')
+Display_Name_for__should_be_one_of__instead_of_other = Wrong Display Name ''{4}'' for {1}#{2}. Valid display is one of {0} choices: {3} (for the language(s) ''{5}'')
+Display_Name_WS_for__should_be_one_of__instead_of_one = Wrong whitespace in Display Name ''{4}'' for {1}#{2}. Valid display is {3} (for the language(s) ''{5}'')
+Display_Name_WS_for__should_be_one_of__instead_of_other = Wrong whitespace in Display Name ''{4}'' for {1}#{2}. Valid display is one of {0} choices: {3} (for the language(s) ''{5}'')
+documentmsg = (document)
+Does_not_match_slice_ = Does not match slice ''{0}'' (discriminator: {1})
+DUPLICATE_ID = Duplicate id value ''{0}''
+DUPLICATE_JSON_PROPERTY_KEY = The JSON property ''{0}'' is a duplicate and will be ignored
+Duplicate_Resource_ = Duplicate Resource {0} of type {3} (existing version {2}, new version {1})
+ED_CONTEXT_INVARIANT_EXPRESSION_ERROR = Error in constraint ''{0}'': {1}
+ED_INVARIANT_DIFF_NO_SOURCE = The invariant {0} defined in the differential must have no source, or the source must be the same as the profile ({1} vs {2})
+ED_INVARIANT_EXPRESSION_CONFLICT = The constraint ''{0}'' has an expression ''{1}'', which differs from the earlier expression provided of ''{2}'' (invariants are allowed to repeat, but cannot differ)
+ED_INVARIANT_EXPRESSION_ERROR = Error in constraint ''{0}'' with expression ''{1}'': {2}
+ED_INVARIANT_KEY_ALREADY_USED = The constraint key ''{0}'' already exists at the location ''{1}'' with a different expression (''{2}'')
+ED_INVARIANT_NO_EXPRESSION = The constraint ''{0}'' has no computable expression, so validators will not be able to check it
+ED_INVARIANT_NO_KEY = The constraint has no key, so the content cannot be validated
+ED_PATH_WRONG_TYPE_MATCH = The path must be ''{0}'' not ''{1}'' when the type list is not constrained
+ED_SEARCH_EXPRESSION_ERROR = Error in search expression ''{0}'': {1}
+element__null_ = Element = null: {0}
+ELEMENT_CANNOT_BE_NULL = The element is not allowed to be ''null''
+element_id__null__on_ = Element id = null: {0} on {1}
+Element_must_have_some_content = Element must have some content
+Error_at__The_target_profile__is_not__valid_constraint_on_the_base_ = Error at {0}#{1}: The target profile {2} is not a valid constraint on the base ({3})
+Error_at_path__in__Type_slicing_with_slicingdiscriminatorcount__1 = Error at path {0} in {1}: Type slicing with slicing.discriminator.count() > 1
+Error_at_path__in__Type_slicing_with_slicingdiscriminatorpath__this = Error at path {0} in {1}: Type slicing with slicing.discriminator.path != ''$this''
+Error_at_path__in__Type_slicing_with_slicingdiscriminatortype__type = Error at path {0} in {1}: Type slicing with slicing.discriminator.type != ''type''
+Error_at_path__in__Type_slicing_with_slicingordered__true = Error at path {0} in {1}: Type slicing with slicing.ordered = true
+Error_at_path__Slice_for_type__has_more_than_one_type_ = Error at path {0}: Slice for type ''{1}'' has more than one type ''{2}''
+Error_at_path__Slice_for_type__has_wrong_type_ = Error at path {0}: Slice for type ''{1}'' has wrong type ''{2}''
+Error_at_path__Slice_name_must_be__but_is_ = Error at path {0}: Slice name must be ''{1}'' but is ''{2}''
+Error_expanding_ValueSet_running_without_terminology_services = Error expanding ValueSet: running without terminology services
+ERROR_GENERATING_SNAPSHOT = Error generating Snapshot: {0} (this usually arises from a problem in the differential)
+Error_generating_table_for_profile__ = Error generating table for profile {0}: {1}
+Error_in_profile__at__Base_isSummary___derived_isSummary__ = Error in profile {0} at {1}: Base isSummary = {2}, derived isSummary = {3}
+Error_parsing_ = Error parsing {0}:{1}
+Error_parsing_JSON_ = Error parsing JSON: {0}
+Error_parsing_JSON_the_primitive_value_must_be_a_boolean = Error parsing JSON: the primitive value must be a boolean
+Error_parsing_JSON_the_primitive_value_must_be_a_number = Error parsing JSON: the primitive value must be a number
+Error_parsing_JSON_the_primitive_value_must_be_a_string = Error parsing JSON: the primitive value must be a string
+Error_parsing_Turtle_ = Error parsing Turtle: {0}
+Error_parsing_XHTML_ = Error parsing XHTML: {0}
+ERROR_PROCESSING_SNAPSHOT = Error processing Snapshot: {0}
+Error_reading__from_package__ = Error reading {0} from package {1}#{2}: {3}
+Error_validating_code_running_without_terminology_services = Unable to validate code ''{0}'' in system ''{1}'' because the validator is running without terminology services
+error_writing_number__to_JSON = Error writing number ''{0}'' to JSON
+EXT_VER_URL_IGNORE = Extension URLs don''t have versions. The validator has ignored the version and processed the extension anyway
+EXT_VER_URL_MISLEADING = The extension URL contains a ''|'' which makes it look like a versioned URL, but it''s not, and this is confusing for implementers
+EXT_VER_URL_NO_MATCH = Extension URLs don''t have versions. The validator wasn''t able to resolve this URL with or without version-based resolution
+EXT_VER_URL_NOT_ALLOWED = The extension URL must not contain a version
+EXT_VER_URL_REVERSION = The extension URL must not contain a version. The extension was validated against version {0} of the extension
+EXTENSION_CONTEXT_UNABLE_TO_CHECK_PROFILE = The extension {0} specifies a context of {1} but the validator cannot check whether the profile is valid or not at this time
+EXTENSION_CONTEXT_UNABLE_TO_FIND_PROFILE = The extension {0} specifies a context of {1} but the validator cannot find that profile
+Extension_EXT_Count_Mismatch = Extensions count mismatch: expected {0} but found {1}
+Extension_EXT_Count_NotFound = Extension count mismatch: unable to find extension: {0}
+Extension_EXT_Fixed_Banned = No extensions allowed, as the specified fixed value doesn''t contain any extensions
+Extension_EXT_Modifier_MismatchN = Extension modifier mismatch: the extension element is not labelled as a modifier, but the underlying extension is
+Extension_EXT_Modifier_MismatchY = Extension modifier mismatch: the extension element is labelled as a modifier, but the underlying extension is not
+Extension_EXT_Modifier_N = The Extension ''{0}'' must not be used as an extension (it''s a modifierExtension)
+Extension_EXT_Modifier_Y = The Extension ''{0}'' must not be used as a modifierExtension (it''s a regular extension)
+Extension_EXT_Simple_ABSENT = The Extension ''{0}'' definition is for a simple extension, so it must contain a value
+Extension_EXT_Simple_WRONG = The Extension ''{0}'' definition is for a simple extension, so it must contain a value, not extensions
+Extension_EXT_SubExtension_Invalid = Sub-extension url ''{0}'' is not defined by the Extension {1}
+Extension_EXT_Type = The Extension ''{0}'' definition allows for the types {1} but found type {2}
+Extension_EXT_Unknown = Unknown extension {0}
+Extension_EXT_Unknown_NotHere = The extension {0} could not be found so is not allowed here
+Extension_EXT_URL_Absolute = Extension.url must be an absolute URL
+Extension_EXT_Url_NotFound = Extension.url is required in order to identify, use and validate the extension
+Extension_EXT_Version_Internal = Extension url ''{0}'' evaluation state invalid
+Extension_EXT_Version_Invalid = Extension url ''{0}'' is not valid (invalid Version ''{1}'')
+Extension_EXT_Version_InvalidId = Extension url ''{0}'' is not valid (invalid Element id ''{1}'')
+EXTENSION_EXT_VERSION_NOTALLOWED = Extension url ''{0}'' is not allowed (Element id ''{1}'' is valid, so check other defined extensions)
+Extension_EXT_Version_NoChange = Extension url ''{0}'' is not valid (Element id ''{1}'' is valid, but cannot be used in a cross-version paradigm because there has been no changes across the relevant versions)
+Extension_EXTM_Context_Wrong = The modifier extension {0} is not allowed to be used at this point (this element is {2}; allowed = {1})
+Extension_EXTM_Context_Wrong_VER = The modifier extension {0} is not allowed to be used at this point (this element is {2}; allowed for this version = {1})
+EXTENSION_EXTM_CONTEXT_WRONG_XVER = The modifier extension {0} from FHIR version {3} is not allowed to be used at this point (this element is {2}; allowed for this version = {1}; this is a warning since contexts may be renamed between FHIR versions)
+Extension_EXTP_Context_Wrong = The extension {0} is not allowed to be used at this point (this element is {2}; allowed for this version = {1})
+Extension_EXTP_Context_Wrong_VER = The extension {0} is not allowed to be used at this point (this element is {2}; allowed for this version = {1})
+EXTENSION_EXTP_CONTEXT_WRONG_XVER = The extension {0} from FHIR version {3} is not allowed to be used at this point (this element is {2}; allowed for this version = {1}; this is a warning since contexts may be renamed between FHIR versions)
+EXTENSION_FHIR_VERSION_EARLIEST = The definition of the extension ''{0}'' specifies that the earliest version it can be used with is {1} (v{2}), but this context of use is version {3} (v{4})
+EXTENSION_FHIR_VERSION_LATEST = The definition of the extension ''{0}'' specifies that the latest version it can be used with is {1} (v{2}), but this context of use is version {3} (v{4})
+Extension_PROF_Type = The Profile ''{0}'' definition allows for the type {1} but found type {2}
+FHIRPATH_ARITHMETIC_MINUS = Error in date arithmetic: Unable to subtract type {0} to {1}
+FHIRPATH_ARITHMETIC_PLUS = Error in date arithmetic: Unable to add type {0} to {1}
+FHIRPATH_ARITHMETIC_QTY = Error in date arithmetic: attempt to add a definite quantity duration time unit {0}
+FHIRPATH_ARITHMETIC_UNIT = Error in date arithmetic: unrecognized time unit {0}
+FHIRPATH_AS_COLLECTION = Attempt to use ''as()'' on more than one item (''{0}'', ''{1}'')
+FHIRPATH_CANNOT_USE = Error evaluating FHIRPath expression: Cannot use {0} in this context because {1}
+FHIRPATH_CANT_COMPARE = Error evaluating FHIRPath expression: Unable to compare values of type {0} and {1}
+FHIRPATH_CHECK_FAILED = Error evaluating FHIRPath expression: Check failed with message ''{0}''
+FHIRPATH_CHOICE_NO_TYPE_SPECIFIER = The expression ''{0}'' refers to an element that is a choice, but doesn''t have an .ofType() so that SQL view runners can pre-determine the full element name
+FHIRPATH_CHOICE_SPURIOUS_TYPE_SPECIFIER = The expression ''{0}'' refers to an element that is not a choice, but has an .ofType(). SQL view runners are likely to pre-determine an incorrect full element name
+FHIRPATH_CODED_ONLY = Error evaluating FHIRPath expression: The function {0} can only be used on ordered string, code, uri, Coding, CodeableConcept but found {1}
+FHIRPATH_COLLECTION_STATUS_CONTEXT = The context is inherently a collection, and so the expression ''{0}'' may fail, create an error, or return false if there is more than one item in the context ({2})
+FHIRPATH_COLLECTION_STATUS_OPERATION_LEFT = The left side is inherently a collection, and so the expression ''{0}'' may fail or return false if there is more than one item in the content being evaluated
+FHIRPATH_COLLECTION_STATUS_OPERATION_RIGHT = The right side is inherently a collection, and so this expression ''{0}'' may fail or return false if there is more than one item in the content being evaluated
+FHIRPATH_COLLECTION_STATUS_PARAMETER = Parameter {1} is inherently a collection, and so the expression ''{0}'' may fail, create an error, or return false if there is more than one item in the parameter value ({2})
+FHIRPATH_CONTINUOUS_ONLY= Error evaluating FHIRPath expression: The function {0} can only be used on a decimal or date type but found {1}
+FHIRPATH_DECIMAL_ONLY = Error evaluating FHIRPath expression: The function {0} can only be used on a decimal but found {1}
+FHIRPATH_DISCRIMINATOR_BAD_NAME = Invalid function name {0}() in discriminator
+FHIRPATH_DISCRIMINATOR_BAD_SYNTAX_CONST = Invalid expression syntax in discriminator (const)
+FHIRPATH_DISCRIMINATOR_BAD_SYNTAX_GROUP = Invalid expression syntax in discriminator (group ''{0}'')
+FHIRPATH_DISCRIMINATOR_CANT_FIND = Unable to resolve discriminator in definitions: ''{0}'' in profile ''{1}'' on element ''{2}'', looking in profile ''{3}''
+FHIRPATH_DISCRIMINATOR_CANT_FIND_EXTENSION = Unable to resolve discriminator ''{0}'' on ''{2}'' found in the definitions because the extension ''{1}'' wasn''t found in the profile ''{3}''
+FHIRPATH_DISCRIMINATOR_MULTIPLE_PROFILES_one =
+FHIRPATH_DISCRIMINATOR_MULTIPLE_PROFILES_other = Error in discriminator at {1}: no children, {0} type profiles
+FHIRPATH_DISCRIMINATOR_MULTIPLE_TYPES_one =
+FHIRPATH_DISCRIMINATOR_MULTIPLE_TYPES_other = Error in discriminator at {1}: no children, {0} types
+FHIRPATH_DISCRIMINATOR_NAME_ALREADY_SLICED = Error in discriminator at {0}: found a sliced element while resolving the fixed value for one of the slices
+FHIRPATH_DISCRIMINATOR_NO_CODE = Invalid use of ofType() in discriminator - Type has no code on {0}
+FHIRPATH_DISCRIMINATOR_NOTYPE = Error in discriminator at {0}: no children, no type
+FHIRPATH_DISCRIMINATOR_RESOLVE_MULTIPLE_TYPES_one =
+FHIRPATH_DISCRIMINATOR_RESOLVE_MULTIPLE_TYPES_other = Invalid use of resolve() in discriminator - {0} possible types on {1} (can only be one)
+FHIRPATH_DISCRIMINATOR_RESOLVE_NO_TYPE = Invalid use of resolve() in discriminator - no type on element {0}
+FHIRPATH_DISCRIMINATOR_RESOLVE_NOT_REFERENCE = Invalid use of resolve() in discriminator - type on {0} is not Reference {1}
+FHIRPATH_DISCRIMINATOR_TYPE_NONE = Invalid use of ofType() in discriminator - no type on element {0}
+FHIRPATH_FOCUS_one =
+FHIRPATH_FOCUS_other = Error evaluating FHIRPath expression: focus for {1} can only have one value, but has {0} values
+FHIRPATH_PARAMETER_CARD_one =
+FHIRPATH_PARAMETER_CARD_other = Error evaluating FHIRPath expression: parameter {1} can only have one value, but has {0} values
+FHIRPATH_HO_HOST_SERVICES = Internal Error evaluating FHIRPath expression: No host services are provided ({0})
+FHIRPATH_INVALID_TYPE = The type {0} is not valid
+FHIRPATH_LEFT_VALUE_one =
+FHIRPATH_LEFT_VALUE_other = Error evaluating FHIRPath expression: left operand to {1} can only have 1 value, but has {0} values ({2})
+FHIRPATH_LEFT_VALUE_WRONG_TYPE = Error evaluating FHIRPath expression: left operand to {0} has the wrong type {1}
+FHIRPATH_LOCATION = (at {0})
+FHIRPATH_MUTIPLE_SORT_TYPE_PROBLEM = Cannot sort the list because the sort expression return both a ''{0}'' and a ''{1}'' (expression = ''{2}'')
+FHIRPATH_MUTIPLE_SORT_TYPE_PROBLEM_NATURAL = Cannot sort a list that contains both a ''{0}'' and a ''{1}'' using natural sort order
+FHIRPATH_MUTIPLE_VALUES_IN_SORT = Multiple values found in return from sort expression ''{0}''
+FHIRPATH_NO_COLLECTION = Error evaluating FHIRPath expression: The function {0} can only be used on a singleton value but found {1}
+FHIRPATH_NO_TYPE = Error evaluating FHIRPath expression: No type provided at {1}
+FHIRPATH_NOT_A_COLLECTION = Found a use of a collection operator on something that is not a collection at ''{0}'' - check that there''s no mistakes in the expression syntax
+FHIRPATH_NOT_IMPLEMENTED = Error evaluating FHIRPath expression: The function {0} is not implemented
+FHIRPATH_NUMERICAL_ONLY = Error evaluating FHIRPath expression: The function {0} can only be used on integer, decimal or Quantity but found {1}
+FHIRPATH_OFTYPE_IMPOSSIBLE = The type specified in ofType() is {1} which is not a possible candidate for the existing types ({0}) in the expression {2}. Check the paths and types to be sure this is what is intended
+FHIRPATH_OP_INCOMPATIBLE = Error evaluating FHIRPath expression {0}: left and right operand have incompatible or invalid types ({1}, {2})
+FHIRPATH_ORDERED_ONLY = Error evaluating FHIRPath expression: The function {0} can only be used on ordered collections
+FHIRPATH_PARAM_WRONG = Error evaluating FHIRPath expression: The expression type {0} is not supported for parameter {1} on function {2}
+FHIRPATH_PRIMITIVE_ONLY = Error evaluating FHIRPath expression: The function {0} can only be used on primitives
+FHIRPATH_REDEFINE_VARIABLE = The variable ''{0}'' cannot be redefined
+FHIRPATH_REFERENCE_ONLY = Error evaluating FHIRPath expression: The function {0} can only be used on ordered string, uri, canonical or Reference but found {1}
+FHIRPATH_RESOLVE_DISCRIMINATOR_CANT_FIND = Problem with use of resolve() - profile {0} on {1} could not be resolved
+FHIRPATH_RESOLVE_DISCRIMINATOR_NO_TARGET_one =
+FHIRPATH_RESOLVE_DISCRIMINATOR_NO_TARGET_other = Invalid use of resolve() in discriminator - {0} possible target type profiles on {1} (can only be one)
+FHIRPATH_RIGHT_VALUE_one =
+FHIRPATH_RIGHT_VALUE_other = Error evaluating FHIRPath expression: right operand to {1} can only have 1 value, but has {0} values
+FHIRPATH_RIGHT_VALUE_WRONG_TYPE = Error evaluating FHIRPath expression: right operand to {0} has the wrong type {1}
+FHIRPATH_STRING_ORD_ONLY = Error evaluating FHIRPath expression: The function {0} can only be used on ordered collection of string, uri, code, id but found {1}
+FHIRPATH_STRING_SING_ONLY = Error evaluating FHIRPath expression: The function {0} can only be used on string, uri, url, code, id but found {1}
+FHIRPATH_UNABLE_BOOLEAN = Unable to evaluate as a boolean: {0}
+FHIRPATH_UNKNOWN_CONSTANT = Error evaluating FHIRPath expression: Invalid FHIRPath Constant {0}
+FHIRPATH_UNKNOWN_CONTEXT = Unknown context evaluating FHIRPath expression: {0}
+FHIRPATH_UNKNOWN_CONTEXT_ELEMENT = Unknown context element evaluating FHIRPath expression: {0}
+FHIRPATH_UNKNOWN_EXTENSION = Reference to an unknown extension - double check that the URL ''{0}'' is correct
+FHIRPATH_UNKNOWN_NAME = Error evaluating FHIRPath expression: The name ''{0}'' is not valid for any of the possible types: {1}
+FHIRPATH_UNKNOWN_TYPE = Error evaluating FHIRPath expression: The type ''{0}'' is unknown or not supported at {1}
+FHIRPATH_WRONG_PARAM_TYPE = Error evaluating FHIRPath expression: The parameter type {2} is not legal for {0} parameter {1}. expecting {3}
+Fixed_Type_Checks_DT_Address_Line = Expected {0} but found {1} line elements
+Fixed_Type_Checks_DT_Name_Family = Expected {0} but found {1} family elements
+Fixed_Type_Checks_DT_Name_Given = Expected {0} but found {1} given elements
+Fixed_Type_Checks_DT_Name_Prefix = Expected {0} but found {1} prefix elements
+Fixed_Type_Checks_DT_Name_Suffix = Expected {0} but found {1} suffix elements
+Found__items_for__resolving_discriminator__from_ = Found {0} items for {1} resolving discriminator {2} from {3}
+getSliceList_should_only_be_called_when_the_element_has_slicing = getSliceList should only be called when the element has slicing
+HTA_LOINC_DESC = LOINC
+HTA_LOINC_MESSAGE = This material contains content from <a href="http://loinc.org">LOINC</a>. LOINC is copyright &copy; 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the <a href="http://loinc.org/license">license</a>. LOINC&reg; is a registered United States trademark of Regenstrief Institute, Inc.
+HTA_SCT_DESC = SNOMED Clinical Terms&reg; (SNOMED CT&reg;)
+HTA_SCT_MESSAGE = This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact <a href="https://www.snomed.org/get-snomed">https://www.snomed.org/get-snomed</a> or <a href="mailto:info@snomed.org">info@snomed.org</a>.
+IG_DEPENDENCY_CAN_VERSION_ALONE = The canonical URL specifies the version ''{0}'', while the dependency does not. If a version is specified, it must be in the explicit version property
+IG_DEPENDENCY_CAN_VERSION_ERROR = The canonical URL specifies the version ''{0}'', while the dependency has version ''{1}''. If a version is specified, it must be the same as in the explicit version property 
+IG_DEPENDENCY_CAN_VERSION_NONE = The canonical URL cannot end in ''|''
+IG_DEPENDENCY_CLASH_CANONICAL = The packageId {0} points to the canonical {1} which is inconsistent with the stated canonical of {2}
+IG_DEPENDENCY_CLASH_PACKAGEID = The canonical URL {0} points to the package {1} which is inconsistent with the stated packageId of {2}
+IG_DEPENDENCY_DIRECT = The URL should refer directly to the ImplementationGuide resource (e.g. include ''/ImplementationGuide/'')
+IG_DEPENDENCY_INVALID_URL = The canonical URL {0} doesn''t point to an actual ImplementationGuide resource
+IG_DEPENDENCY_EXCEPTION = Exception checking package version consistency: {0}
+IG_DEPENDENCY_INVALID_PACKAGE_VERSION = The version {0} is not a valid NPM package version
+IG_DEPENDENCY_INVALID_PACKAGEID = The packageId {0} is not valid
+IG_DEPENDENCY_NO_PACKAGE = No NPM package id could be determined so the version consistency can't be checked
+IG_DEPENDENCY_NO_VERSION = No version was specified for the package so the version consistency can't be checked
+IG_DEPENDENCY_PACKAGE_UNKNOWN = The package {0} could not be found so the version consistency can't be checked 
+IG_DEPENDENCY_VERSION_ERROR = The ImplementationGuide is based on FHIR version {0} but package {1} is based on FHIR version {2}. Use the package {3} instead
+IG_DEPENDENCY_VERSION_WARNING = The ImplementationGuide is based on FHIR version {0} but package {1} is based on FHIR version {2}. In general, this version mismatch should be avoided - some tools will try to make this work with variable degrees of success, but others will not even try
+IG_DEPENDENCY_VERSION_WARNING_OLD = The ImplementationGuide uses package {0} released on {2}, but the most recent appropriate version is {1}. This reference is getting old and the more recent version should be considered
+IG_HL7_FMM_SHOULD = HL7 Implementation Guides should state their maturity explicitly using the extension http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
+IG_HL7_STANDARDS_STATUS_REQUIRED = HL7 Implementation Guides must state their status explicitly using the extension http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
+IG_HL7_WG_REQUIRED = HL7 Implementation Guides must state their owning workgroup explicitly using the extension http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
+IG_NO_VERSION = No fhir version was specified for the IG so the version consistency can't be checked
+ILLEGAL_COMMENT_TYPE = The fhir_comments property must be an array of strings
+Illegal_path__in_differential_in__illegal_character_ = Invalid path ''{0}'' in differential in {1}: invalid character ''{2}''
+Illegal_path__in_differential_in__illegal_characters_ = Invalid path ''{0}'' in differential in {1}: invalid characters []
+Illegal_path__in_differential_in__must_start_with_ = Invalid path ''{0}'' in input differential in {1}: must start with {2}.{3}
+Illegal_path__in_differential_in__name_portion_exceeds_64_chars_in_length = Invalid path ''{0}'' in differential in {1}: name portion exceeds 64 chars in length
+Illegal_path__in_differential_in__name_portion_mising_ = Invalid path ''{0}'' in differential in {1}: name portion missing (''..'')
+Illegal_path__in_differential_in__no_unicode_whitespace = Invalid path ''{0}'' in differential in {1}: no unicode whitespace
+ILLEGAL_PROPERTY = The property ''{0}'' is invalid
+Internal_error___type_not_known_ = Internal error - type not known {0}
+Internal_INT_Bad_Type = Unhandled fixed value type {0}
+INV_FAILED = Constraint failed: {0}: ''{1}''
+INV_FAILED_SOURCE = Constraint failed: {0}: ''{1}'' (defined in {2})
+INVALID_DISPLAY_NAME = Invalid displayLanguage: ''{0}''
+Invalid_slicing__there_is_more_than_one_type_slice_at__but_one_of_them__has_min__1_so_the_other_slices_cannot_exist=Invalid slicing: there is more than one type slice at {0}, but one of them ({1}) has min = 1, so the other slices cannot exist
+JSON_COMMA_EXTRA = There is an extra comma at the end of the {0} in the JSON
+JSON_COMMA_MISSING = A Comma is missing in the JSON
+JSON_COMMENTS_NOT_ALLOWED = Comments are not allowed in JSON
+JSON_PROPERTY_NO_QUOTES = The JSON property ''{0}'' has no quotes around the name of the property
+JSON_PROPERTY_VALUE_NO_QUOTES = The JSON property ''{0}'' has no quotes around the value of the property ''{1}''
+Language_XHTML_Lang_Different1 = Resource has a language ({0}), and the XHTML has a lang ({1}), but they differ
+Language_XHTML_Lang_Different2 = Resource has a language ({0}), and the XHTML has an xml:lang ({1}), but they differ
+Language_XHTML_Lang_Missing1 = Resource has a language, but the XHTML does not have an lang or an xml:lang tag (needs both - see https://www.w3.org/TR/i18n-html-tech-lang/#langvalues)
+Language_XHTML_Lang_Missing2 = Resource has a language, but the XHTML does not have a lang tag (needs both lang and xml:lang - see https://www.w3.org/TR/i18n-html-tech-lang/#langvalues)
+Language_XHTML_Lang_Missing3 = Resource has a language, but the XHTML does not have an xml:lang tag (needs both lang and xml:lang - see https://www.w3.org/TR/i18n-html-tech-lang/#langvalues)
+LIQUID_SYNTAX_COLON = Exception evaluating {0}: limit is not followed by '':''
+LIQUID_SYNTAX_EXPECTING = Script {0}: Found ''{1}'' expecting ''{2}'' parsing cycle
+LIQUID_SYNTAX_INCLUDE = Script {0}: Error reading include: {1}
+LIQUID_SYNTAX_LOOP = Script {0}: Error reading loop: {1}
+LIQUID_SYNTAX_NOTERM = Script {0}: Unterminated Liquid statement {1}
+LIQUID_SYNTAX_NUMBER = Exception evaluating {0}: limit is not followed by a number
+LIQUID_SYNTAX_UNEXPECTED = Exception evaluating {0}: unexpected content at {1}
+LIQUID_SYNTAX_UNTERMINATED = Script {0}: Found unterminated string parsing cycle
+LIQUID_UNKNOWN_FILTER = Unknown Liquid filter ''{0}''
+LIQUID_UNKNOWN_FLOW_STMT = Script {0}: Unknown flow control statement ''{1}''
+LIQUID_UNKNOWN_NOEND = Script {0}: Found end of script looking for {1}
+LIQUID_UNKNOWN_SYNTAX = Unexpected syntax parsing liquid statement
+LIQUID_VARIABLE_ALREADY_ASSIGNED = Liquid Exception: The variable ''{0}'' already has an assigned value
+LIQUID_VARIABLE_ILLEGAL = Liquid Exception: The variable name ''{0}'' cannot be used
+LOGICAL_MODEL_NAME_MISMATCH = The name ''{0}'' does not match the expected name ''{1}''
+LOGICAL_MODEL_QNAME_MISMATCH = The QName ''{0}'' does not match the expected QName ''{1}''
+MEASURE_M_CRITERIA_CQL_ELM_NOT_VALID = = Error in {0}: Compiled version of CQL is not valid
+MEASURE_M_CRITERIA_CQL_ERROR = Error in {0}: ''{1}''
+MEASURE_M_CRITERIA_CQL_LIB_DUPL = Multiple matching libraries found for the namespace {0}
+MEASURE_M_CRITERIA_CQL_LIB_NOT_FOUND = No matching Library found for the namespace {0}
+MEASURE_M_CRITERIA_CQL_NO_ELM = Error in {0}: No compiled version of CQL found
+MEASURE_M_CRITERIA_CQL_NO_LIB = No CQL Libraries found on this Measure
+MEASURE_M_CRITERIA_CQL_NOT_FOUND = The function {1} does not exist in the library {0}
+MEASURE_M_CRITERIA_CQL_ONLY_ONE_LIB = If the CQL expression does not include a namespace, there can only be one Library for the measure
+MEASURE_M_CRITERIA_UNKNOWN = The expression language {0} is not supported, so can''t be validated
+MEASURE_M_GROUP_CODE = Groups should have codes when there is more than one group
+MEASURE_M_GROUP_POP = Measure Groups should have at least one population
+MEASURE_M_GROUP_POP_NO_CODE = A measure group population should have a code when there is more than one population
+MEASURE_M_GROUP_STRATA_COMP_NO_CODE = A measure group stratifier component should have a code when there is more than one population
+MEASURE_M_GROUP_STRATA_NO_CODE = A measure group stratifier should have a code when there is more than one population
+MEASURE_M_LIB_UNKNOWN = The Library {0} could not be resolved, so expression validation may not be correct
+MEASURE_M_NO_GROUPS = A measure should contain at least one group
+MEASURE_MR_GRP_CODE_MISMATCH = The linkId ''{0}'' links this group to a measure group that has a different code (''{1}'' vs ''{2}'')
+MEASURE_MR_GRP_DUPL_CODE = The code for this group is duplicated with another group
+MEASURE_MR_GRP_MISSING_BY_CODE = The MeasureReport does not include a group for the group with code ''{0}''
+MEASURE_MR_GRP_MISSING_BY_CODE_R5 = The MeasureReport does not include a group for the group with linkId ''{1}'' and code ''{0}''
+MEASURE_MR_GRP_NO_CODE = Group should have a code that matches the group definition in the measure
+MEASURE_MR_GRP_NO_CODE_R5 = Group should have a code or linkId that matches the group definition in the measure
+MEASURE_MR_GRP_NO_USABLE_CODE = None of the codes provided are usable for comparison - need both system and code on at least one code
+MEASURE_MR_GRP_NO_WRONG_CODE = The code provided ({0}) does not match the code specified in the measure report ({1})
+MEASURE_MR_GRP_NO_WRONG_LINKID = The linkId provided ({0}) does not match the code specified in the measure report ({1})
+MEASURE_MR_GRP_POP_CODE_MISMATCH = The linkId ''{0}'' links this group population to a measure group population that has a different code (''{1}'' vs ''{2}'')
+MEASURE_MR_GRP_POP_COUNT_CANT_CHECK = Unable to check the stated count {0} because the subject list cannot be fully processed ({1})
+MEASURE_MR_GRP_POP_COUNT_MISMATCH = Mismatch between count {0} and number of subjects {1}
+MEASURE_MR_GRP_POP_COUNT_NO_REF = Subject reference has no actual reference
+MEASURE_MR_GRP_POP_COUNT_NO_REF_RES = Subject reference {0} could not be resolved, and so could not be processed
+MEASURE_MR_GRP_POP_COUNT_REF_UNPROCESSIBLE = Subject reference {0} resolved to a {1}, which could not be processed
+MEASURE_MR_GRP_POP_COUNT_UNRESOLVED = Subject reference {0} could not be resolved, and the apparent type is {1} which could not be processed
+MEASURE_MR_GRP_POP_DUPL_CODE = The code for this group population is duplicated with another group
+MEASURE_MR_GRP_POP_MISSING_BY_CODE = The MeasureReport does not include a population for the population with linkId ''{0}'' and code ''{1}''
+MEASURE_MR_GRP_POP_NO_CODE = Group should have a code that matches the group population definition in the measure
+MEASURE_MR_GRP_POP_NO_CODE_R5 = Group should have a code or linkId that matches the group population definition in the measure
+MEASURE_MR_GRP_POP_NO_COUNT = Count should be present for reports where type is not ''subject-list''
+MEASURE_MR_GRP_POP_NO_SUBJECTS = Reports where type is not ''subject-list'' don''t have subjects listed
+MEASURE_MR_GRP_POP_UNK_CODE = The code for this group population has no match in the measure definition
+MEASURE_MR_GRP_POP_UNK_LINKID = The linkId ''{0}'' for this group population has no match in the measure definition
+MEASURE_MR_GRP_STRAT_CODE_MISMATCH = The linkId ''{0}'' links this group stratifier to a measure group that has a different code (''{1}'' vs ''{2}'')
+MEASURE_MR_GRP_STRAT_DUPL_CODE = The code for this group stratifier is duplicated with another group
+MEASURE_MR_GRP_STRAT_MISSING_BY_CODE = The MeasureReport does not include a stratifier for the stratifier with code ''{0}'' (id = ''{2}'')
+MEASURE_MR_GRP_STRAT_MISSING_BY_CODE_R5 = The MeasureReport does not include a stratifier for the stratifier with linkId ''{1}'' and code ''{0}'' (id = ''{2}'')
+MEASURE_MR_GRP_STRAT_NO_CODE = Group should have a code that matches the group stratifier definition in the measure
+MEASURE_MR_GRP_STRAT_NO_CODE_R5 = Group should have a code or linkId that matches the group stratifier definition in the measure
+MEASURE_MR_GRP_STRAT_UNK_CODE = The code for this group stratifier has no match in the measure definition
+MEASURE_MR_GRP_STRAT_UNK_LINKID = The linkId ''{0}'' for this group stratifier has no match in the measure definition
+MEASURE_MR_GRP_UNK_CODE = The code ''{0}'' for this group has no match in the measure definition
+MEASURE_MR_GRP_UNK_LINKID = The linkId ''{0}'' for this group has no match in the measure definition
+Measure_MR_M_None = No Measure is identified, so no validation can be performed against the Measure
+Measure_MR_M_NotFound = The Measure ''{0}'' could not be resolved, so no validation can be performed against the Measure
+MEASURE_MR_M_SCORING_UNK = The scoring system in this measure is unknown, so the measureScore values cannot be checked
+MEASURE_MR_SCORE_FIXED = This value is fixed by the Measure to ''{0}''
+MEASURE_MR_SCORE_PROHIBITED_MS = No measureScore when the scoring of the message is ''cohort''
+MEASURE_MR_SCORE_PROHIBITED_RT = No measureScore when the type of the report is ''data-collection''
+MEASURE_MR_SCORE_REQUIRED = A measureScore is required when the Measure.scoring={0}
+MEASURE_MR_SCORE_UNIT_PROHIBITED = A measureScore for this Measure Scoring ({0}) should not have units
+MEASURE_MR_SCORE_UNIT_REQUIRED = A unit should be present when the scoring type is {0}
+MEASURE_MR_SCORE_VALUE_INVALID_01 = The value is invalid - it must be between 0 and 1
+MEASURE_MR_SCORE_VALUE_REQUIRED = A value is required when the Measure.scoring = {0}
+MEASURE_SHAREABLE_EXTRA_MISSING = Published measures SHOULD conform to the ShareableMeasure profile, which says that the element Measure.{0} should be present, but it is not
+MEASURE_SHAREABLE_EXTRA_MISSING_HL7 = Measures published by HL7 SHALL conform to the ShareableMeasure profile, which says that the element Measure.{0} should be present, but it is not
+MEASURE_SHAREABLE_MISSING = Published measures SHOULD conform to the ShareableMeasure profile, which says that the element Measure.{0} is mandatory, but it is not present
+MEASURE_SHAREABLE_MISSING_HL7 = Measures published by HL7 SHALL conform to the ShareableMeasure profile, which says that the element Measure.{0} is mandatory, but it is not present
+Meta_RES_Security_Duplicate = Duplicate Security Label {0}
+MSG_DEPENDS_ON_DEPRECATED = The {0} {1} is deprecated
+MSG_DEPENDS_ON_DEPRECATED_NOTE = The {0} {1} is deprecated with the note: ''{2}''
+MSG_DEPENDS_ON_DRAFT = The {0} {1} is a draft resource
+MSG_DEPENDS_ON_EXPERIMENTAL = The {0} {1} is an experimental resource
+MSG_DEPENDS_ON_EXTENSION = extension
+MSG_DEPENDS_ON_PROFILE = profile
+MSG_DEPENDS_ON_RETIRED = The {0} {1} is retired
+MSG_DEPENDS_ON_WITHDRAWN = The {0} {1} is withdrawn
+MSG_DEPRECATED = Reference to deprecated {2} {0}
+MSG_DEPRECATED_SRC = Reference to deprecated {2} {0} from {1}
+MSG_DRAFT = Reference to draft {2} {0}
+MSG_DRAFT_SRC = Reference to draft {2} {0} from {1}
+MSG_EXPERIMENTAL = Reference to experimental {2} {0}
+MSG_EXPERIMENTAL_SRC = Reference to experimental {2} {0} from {1}
+MSG_RETIRED = Reference to retired {2} {0}
+MSG_RETIRED_SRC = Reference to retired {2} {0} from {1}
+MSG_WITHDRAWN = Reference to withdrawn {2} {0}
+MSG_WITHDRAWN_SRC = Reference to withdrawn {2} {0} from {1}
+MULTIPLE_LOGICAL_MODELS_one=
+MULTIPLE_LOGICAL_MODELS_other={0} Logical Models found in supplied profiles, so unable to parse logical model (can only be one, found {1})
+MustSupport_VAL_MustSupport = The element {0} is not marked as ''mustSupport'' in the profile {1}. Consider not using the element, or marking the element as must-Support in the profile
+NARRATIVE_NOT_TRANSLATED = "The narrative includes custom content for the default language ({0}), but does not include translated content for the {1} language, so the default language has been used
+Named_items_are_out_of_order_in_the_slice = Named items are out of order in the slice
+NDJSON_EMPTY_LINE_WARNING = The NDJSON source contains an empty line. This may not be accepted by some processors
+needs_a_snapshot = Needs a snapshot
+no_base_profile_provided = No base profile provided
+no_derived_structure_provided = No derived structure provided
+No_Expansion_Parameters_provided = No Expansion Parameters provided
+No_ExpansionProfile_provided = No ExpansionProfile provided
+No_Parameters_provided_to_expandVS = No Parameters provided to expandVS
+No_path_on_element_Definition__in_ = No path on element Definition {0} in {1}
+No_path_on_element_in_differential_in_ = No path on element in differential in {0}
+No_path_value_on_element_in_differential_in_ = No path value on element in differential in {0}
+No_processing_instructions_allowed_in_resources = No processing instructions allowed in resources
+No_reference_resolving_discriminator__from_ = No reference resolving discriminator {0} from {1}
+No_type_found_on_ = No type found on ''{0}''
+no_url_in_expand_value_set = No url in expand value set
+no_url_in_expand_value_set_2 = No url in expand value set 2
+NO_VALID_DISPLAY_AT_ALL = Cannot validate display ''{0}'' for {1}#{2} in language {3}: No displays are known
+NO_VALID_DISPLAY_FOUND_LANG_NONE_one = ''{5}'' is the default display; the code system {1} has no Display Names for the language {4}
+NO_VALID_DISPLAY_FOUND_LANG_NONE_other = ''{5}'' is the default display; the code system {1} has no Display Names found for the language {4}
+NO_VALID_DISPLAY_FOUND_LANG_SOME_one = ''{5}'' is the default display; no valid Display Names found for {1}#{2} in the language {4}
+NO_VALID_DISPLAY_FOUND_LANG_SOME_other = ''{5}'' is the default display; no valid Display Names found for {1}#{2} in the language {4}
+NO_VALID_DISPLAY_FOUND_NONE_FOR_LANG_ERR = Wrong Display Name ''{0}'' for {1}#{2}. There are no valid display names found for language(s) ''{3}''. Default display is ''{4}''
+NO_VALID_DISPLAY_FOUND_NONE_FOR_LANG_OK = There are no valid display names found for the code {1}#{2} for language(s) ''{3}''. The display is ''{4}'' which is the default language display
+NO_VALID_DISPLAY_FOUND_one = No valid Display Names found for {1}#{2} in the language {4}
+NO_VALID_DISPLAY_FOUND_other = No valid Display Names found for {1}#{2} in the languages {4}
+No_validator_configured = No validator configured
+no_value_set = ValueSet has no url property
+Node_type__is_not_allowed = Node type {0} is not allowed
+None_of_the_provided_codes_are_in_the_value_set_one = The provided code {2} was not found in the value set ''{1}''
+None_of_the_provided_codes_are_in_the_value_set_other = None of the provided codes [{2}] are in the value set ''{1}''
+Not_done_yet = Not done yet
+Not_done_yet__resolve__locally_2 = Not done yet - resolve {0} locally (2)
+not_done_yet_cant_fetch_ = Not done yet: can''t fetch {0}
+Not_done_yet_ValidatorHostServicescheckFunction = Not done yet (ValidatorHostServices.checkFunction)
+Not_done_yet_ValidatorHostServicesconformsToProfile_when_item_is_not_an_element = Not done yet (ValidatorHostServices.conformsToProfile), when item is not an element
+Not_done_yet_ValidatorHostServicesexecuteFunction = Not done yet (ValidatorHostServices.executeFunction)
+Not_handled_yet_sortElements_ = Not handled yet (sortElements: {0}:{1})
+not_the_right_kind_of_structure_to_generate_schematrons_for = Not the right kind of structure to generate schematrons for
+null_min = Null min
+OBJECT_CANNOT_BE_KEYED_ARRAY_CHILD_COUNT = This object cannot be an keyed Array in Json because it does not have two children in the definitions (children = {0})
+OBJECT_CANNOT_BE_KEYED_ARRAY_NO_CHOICE = This object is defined as a keyed Array in Json but the value property named in the definitions is a choice - this is not supported (value property = {0})
+OBJECT_CANNOT_BE_KEYED_ARRAY_NO_LIST = This object is defined as a keyed Array in Json but the value property named in the definitions is a list - this is not supported (value property = {0})
+OBJECT_CANNOT_BE_KEYED_ARRAY_PROP_NAME = This object is defined as a keyed Array in Json but the definition does not name the first child element as the key (children = {0})
+OBJECT_CANNOT_BE_KEYED_ARRAY_PROP_TYPE = This object is defined as a keyed Array in Json but the key property named in the definitions is not a primitive type (children = {0}, type = {1})
+Object_must_have_some_content = Object must have some content
+OPDEF_PROFILE_NO_FIXED = The parameter name for the slice ''{1}'' in the {0} profile is not fixed
+OPDEF_PROFILE_NO_SLICE = The slice ''{1}'' in the {0} profile does not have a sub-slice for the parameter name
+OPDEF_PROFILE_NOT_FOUND = The ''{0}'' profile ''{1}'' can not be resolved
+OPDEF_PROFILE_NOT_IN_PARAM = The ''{0}'' profile {2} defines a parameter ''{1}'' but this is not in the parameters list in the operation definition
+OPDEF_PROFILE_NOT_IN_PROFILE = The ''{0}'' profile does not have a parameter ''{1}'' but it is in the parameters list in the operation definition
+OPDEF_PROFILE_NOT_PARAMETERS = The ''{0}'' profile ''{1}'' is not a profile on the ''Parameters'' resource
+OPDEF_PROFILE_NOT_VALUE_MISMATCH = The parameter ''{1}'' has a value for ''{2}'' of ''{4}'' in the ''{0}'' profile {4} that is different to ''{3}'' which is the value in the parameter definition in the operation definition
+OPDEF_PROFILE_PROFILE_NOT_IN_PARAMS = The target profile ''{2}'' is allowed for the parameter ''{1}'' in the ''{0}'' profile {4} but is not in the list of target profiles for the parameter in the operation definition: {3}
+OPDEF_PROFILE_PROFILE_NOT_IN_PROFILE = The target profile ''{2}'' is not allowed for the parameter ''{1}'' in the ''{0}'' profile but is in the list of target profiles for the parameter in the operation definition (profile target profiles = {3})
+OPDEF_PROFILE_TYPE_NOT_IN_PARAMS = The type ''{2}'' is allowed for the parameter ''{1}'' in the ''{0}'' profile {4} but is not in the list of allowed types for the parameter in the operation definition: {3}
+OPDEF_PROFILE_TYPE_NOT_IN_PROFILE = The type ''{2}'' is not allowed for the parameter ''{1}'' in the ''{0}'' profile {4} but is in the list of allowed types for the parameter in the operation definition (allowed types = {3})
+PACKAGE_VERSION_MISMATCH = FHIR Version mismatch in package {0}: version is {2} but must be {1} (path: {3})
+Parser_Type__not_supported = Parser Type {0} not supported
+PATTERN_CHECK_STRING = The pattern [{0}] defined in the profile {1} not found. Issues: {2}
+PRIMITIVE_MUSTHAVEVALUE_MESSAGE = The element definition ``{0}`` in the profile ''{1}'' requires that a value be present in this element
+PRIMITIVE_TOO_SHORT = Value ''{0}'' is shorter than permitted minimum length of {1}
+PRIMITIVE_VALUE_ALTERNATIVES_MESSAGE_one = The element definition ``{0}`` in the profile ''{1}'' requires that if a value is not present, the extension ''{2}'' must be present
+PRIMITIVE_VALUE_ALTERNATIVES_MESSAGE_other = The element definition ``{0}`` in the profile ''{1}'' requires that if a value is not present, one of the extensions ''{2}'' must be present
+Problem_evaluating_slicing_expression_for_element_in_profile__path__fhirPath___ = Problem evaluating slicing expression for element in profile {0} path {1} (fhirPath = {2}): {3}
+Problem_processing_expression__in_profile__path__ = Problem processing expression ''{0}'' in profile ''{1}'' at path ''{2}'': {3}
+Profile___base__could_not_be_resolved = Profile {0} ({1}) base {2} could not be resolved
+Profile___element__Error_generating_snapshot_ = Profile {0} ({1}), element {2}. Error generating snapshot: {3}
+Profile___Error_generating_snapshot = Profile {0} ({1}). Error generating snapshot
+Profile___has_no_base_and_no_snapshot = Profile {0} ({1}) has no base and no snapshot
+Profile__does_not_match_for__because_of_the_following_profile_issues__ = Profile {0} does not match for {1} because of the following profile issues: {2}
+Profile_based_discriminators_must_have_a_type__in_profile_ = Profile based discriminators must have a type ({0} in profile {1})
+Profile_based_discriminators_must_have_a_type_with_a_profile__in_profile_ = Profile based discriminators must have a type with a profile ({0} in profile {1})
+PROFILE_COMPLIES_WITH_BAD_ELEMENT = The {0} ''{1}'' is not allowed in the claimed profile
+PROFILE_COMPLIES_WITH_BAD_TYPE = The type ''{0}'' is not allowed in the claimed profile
+PROFILE_COMPLIES_WITH_MISSING = There is no profile entry for the element {0} that is found in the claimed profile
+PROFILE_COMPLIES_WITH_MISSING_ELEMENT = The {0} ''{1}'' is defined in the claimed profile, but missing
+PROFILE_COMPLIES_WITH_NO_VS = The ValueSet ''{0}'' cannot be found so the claim cannot be checked
+PROFILE_COMPLIES_WITH_NO_VS_EXP = The ValueSet ''{0}'' cannot be expanded so the claim cannot be checked: {1}
+PROFILE_COMPLIES_WITH_NO_VS_NO = The valueSet {0} includes codes not allowed in the claimed profile which has value set {1} (codes: {2})
+PROFILE_COMPLIES_WITH_NOT_VALID = The {0} value of ''{2}'' on the path {3} does not comply with the value ''{1}'' from the claimed profile
+PROFILE_COMPLIES_WITH_SLICING_DISCRIMINATOR =  Mismatch in slicing rules at {0}: the discriminator ''{0}:{1}'' was not found
+PROFILE_COMPLIES_WITH_SLICING_EXTRA_SLICE = Mismatch in slicing at {0}: extra slice ''{1}'' not found in the claimed profile
+PROFILE_COMPLIES_WITH_SLICING_NO_SLICE = Mismatch in slicing at {0}: no slice found for the discriminator {1} with the values {2}
+PROFILE_COMPLIES_WITH_SLICING_ORDER = Mismatch in slicing rules at {0}: not ordered when the claimed profile has ordered
+PROFILE_COMPLIES_WITH_SLICING_RULES = Mismatch in slicing rules at {0}: ''{2}'' when the claimed profile has ''{1}''
+PROFILE_COMPLIES_WITH_SLICING_UNSLICED = Mismatch in slicing at {0}: no slicing found when the claimed profile has slicing
+PROFILE_COMPLIES_WITH_WRONG_TYPE = The type found in the claimed profile is ''{0}'' not ''{1}''
+Profile_EXT_Not_Here = The extension {0} is not allowed to be used at this point (based on context invariant ''{1}'')
+Profile_VAL_MissingElement = Missing element ''{0}'' - required by fixed value assigned in profile {1}
+Profile_VAL_NotAllowed = The element {0} is present in the instance but not allowed in the applicable {1} specified in profile
+QUESTIONNAIRE_Q_DERIVATION_TYPE_IGNORED = The derivation type ''{0}'' means that no derivation checking has been performed against this questionnaire
+QUESTIONNAIRE_Q_DERIVATION_TYPE_UNKNOWN = The derivation type ''{0}'' is unknown, which means that no derivation checking has been performed against this questionnaire
+Questionnaire_Q_EnableWhen_After = The target of this enableWhen rule ({0}) comes after the question itself
+Questionnaire_Q_EnableWhen_IsInner = Questions with an enableWhen cannot refer to an inner question for its enableWhen condition
+Questionnaire_Q_EnableWhen_NoLink = Questions with an enableWhen must have a value for the question link
+Questionnaire_Q_EnableWhen_NoTarget = Unable to find an item with the linkId ''{0}'' which is referenced in the enableWhen for ''{1}''
+Questionnaire_Q_EnableWhen_Self = Target for this question enableWhen can''t reference itself
+QUESTIONNAIRE_Q_ITEM_DERIVED_ANSWER_OPTIONS = The item with linkId ''{1}'' found in questionnaire ''{0}'' has answerOptions, so this item must have some too
+QUESTIONNAIRE_Q_ITEM_DERIVED_ANSWER_OPTIONS_NEW = The item with linkId ''{1}'' found in questionnaire ''{0}'' does not have this answerOption, so it is not valid
+QUESTIONNAIRE_Q_ITEM_DERIVED_DEFINITION = The item with linkId ''{1}'' found in questionnaire ''{0}'' has the definition ''{2}'', so this should be repeated here
+QUESTIONNAIRE_Q_ITEM_DERIVED_MAXLENGTH = The item with linkId ''{1}'' found in questionnaire ''{0}'' has the definition ''{2}'', so this item must also have a max length
+QUESTIONNAIRE_Q_ITEM_DERIVED_NC_ANSWER_TYPE = The item with linkId ''{1}'' found in questionnaire ''{0}'' has answer{2}, while this has answer{3}. This might be valid, but the vaidator can''t check that (yet?)
+QUESTIONNAIRE_Q_ITEM_DERIVED_NC_DEFINITION = The item with linkId ''{1}'' found in questionnaire ''{0}'' has the definition ''{2}''. Is it intended to change this?
+QUESTIONNAIRE_Q_ITEM_DERIVED_NC_MAXLENGTH = The item with linkId ''{1}'' found in questionnaire ''{0}'' has the maxLength of ''{2}'', so the max length cannot be greater than that
+QUESTIONNAIRE_Q_ITEM_DERIVED_NC_REPEATS = The item with linkId ''{1}'' found in questionnaire ''{0}'' does not repeat, so it cannot repeat here
+QUESTIONNAIRE_Q_ITEM_DERIVED_NC_REQUIRED = The item with linkId ''{1}'' found in questionnaire ''{0}'' is required, so it must be required here
+QUESTIONNAIRE_Q_ITEM_DERIVED_NC_TYPE = The item with linkId ''{1}'' found in questionnaire ''{0}'' has the type ''{2}'', and this cannot change to ''{3}''
+QUESTIONNAIRE_Q_ITEM_DERIVED_NI_ANSWER_VS = The validator can''t check derived item value set consistency (yet?)
+QUESTIONNAIRE_Q_ITEM_NOT_DERIVED = No item with linkId ''{1}'' found in questionnaire ''{0}''
+QUESTIONNAIRE_Q_NO_DERIVATION_TYPE = The questionnaire ''{0}'' has no derivation type specified using the ''http://hl7.org/fhir/StructureDefinition/questionnaire-derivationType'' extension, so derivation has not been checked
+QUESTIONNAIRE_Q_NO_DERIVATION_TYPE_VALUE = The derivation extension has no value
+QUESTIONNAIRE_Q_UNKNOWN_DERIVATION = The questionnaire ''{0}'' referred to in the derivation could not be found
+Questionnaire_QR_Item_BadOption = The code ''{1}'' in the system ''{0}'' is not in the options value set ({2}) specified by the questionnaire. Terminology Error: {3}
+QUESTIONNAIRE_QR_ITEM_BADOPTION_CS = The code provided {1} cannot be validated in the options value set ({2}) in the questionnaire because the system {0} could not be found
+Questionnaire_QR_Item_Coding = Error {0} validating Coding against Questionnaire Options
+Questionnaire_QR_Item_CodingNoOptions = Cannot validate Coding option because no option list is provided
+Questionnaire_QR_Item_DateNoOptions = Cannot validate date answer option because no option list is provided
+Questionnaire_QR_Item_Display = Items not of type DISPLAY should not have items - linkId {0}
+Questionnaire_QR_Item_Group = Items of type {0} should not have answers
+Questionnaire_QR_Item_GroupAnswer = Items not of type group should not have items outside answers (use answer.item not .item)
+Questionnaire_QR_Item_IntNoOptions = Cannot validate integer answer option because no option list is provided
+Questionnaire_QR_Item_Missing = No response answer found for required item ''{0}''
+Questionnaire_QR_Item_NoCoding = The code {0}::{1} is not in the set of permitted values
+Questionnaire_QR_Item_NoDate = The date {0} is not in the set of permitted values
+Questionnaire_QR_Item_NoInteger = The integer {0} is not in the set of permitted values
+Questionnaire_QR_Item_NoLinkId = No LinkId, so can''t be validated
+Questionnaire_QR_Item_NoOptions = Cannot validate options because no option or options are provided
+Questionnaire_QR_Item_NoOptionsCoding = Option list has no option values of type coding
+Questionnaire_QR_Item_NoOptionsDate = Option list has no option values of type date
+Questionnaire_QR_Item_NoOptionsInteger = Option list has no option values of type integer
+Questionnaire_QR_Item_NoOptionsString = Option list has no option values of type string
+Questionnaire_QR_Item_NoOptionsTime = Option list has no option values of type time
+Questionnaire_QR_Item_NoString = The string {0} is not in the set of permitted values
+Questionnaire_QR_Item_NotEnabled = Item has answer (2), even though it is not enabled {0}
+Questionnaire_QR_Item_NotEnabled2 = Item has answer, even though it is not enabled (item id = ''{0}'')
+Questionnaire_QR_Item_NotFound = LinkId ''{0}'' not found in questionnaire
+Questionnaire_QR_Item_NoTime = The time {0} is not in the set of permitted values
+Questionnaire_QR_Item_NoType = Definition for item {0} does not contain a type
+Questionnaire_QR_Item_OnlyOneA = Only one response answer item with this linkId allowed
+Questionnaire_QR_Item_OnlyOneI_one =
+Questionnaire_QR_Item_OnlyOneI_other = Only one response item with the linkId {1} allowed - found {0} items
+Questionnaire_QR_Item_Order = Structural Error: items are out of order
+QUESTIONNAIRE_QR_ITEM_STRING_IN_CODING = The string value ''{0}'' matches an entry in the list of valid Codings, so this is probably an error
+Questionnaire_QR_Item_StringNoOptions = Cannot validate string answer option because no option list is provided
+Questionnaire_QR_Item_Text = If text exists, it must match the questionnaire definition for linkId {0}
+Questionnaire_QR_Item_TimeNoOptions = Cannot validate time answer option because no option list is provided
+Questionnaire_QR_Item_WrongType_one = Answer value must be of the type {1} not {2}
+Questionnaire_QR_Item_WrongType_other = Answer value must be one of the {0} types {1} not {2}
+Questionnaire_QR_Q_None = No questionnaire is identified, so no validation can be performed against the base questionnaire
+Questionnaire_QR_Q_NotFound = The questionnaire ''{0}'' could not be resolved, so no validation can be performed against the base questionnaire
+Reference__refers_to_a__not_a_ValueSet = Reference {0} refers to a {1} not a ValueSet
+Reference_REF_Aggregation = Reference is {0} which isn''t supported by the specified aggregation mode(s) for the reference ({1})
+Reference_REF_BadTargetType = Invalid Resource target type. Found {0}, but expected one of ({1})
+Reference_REF_BadTargetType2 = The type ''{0}'' implied by the reference URL {1} is not a valid Target for this element (must be one of {2})
+Reference_REF_CantMatchChoice = Unable to find a profile match for {0} among choices: {1}
+Reference_REF_CantMatchType = Unable to find a profile match for {0} (by type) among choices: {1}
+Reference_REF_CantResolve = Unable to resolve resource with reference ''{0}''
+Reference_REF_CantResolveProfile = Unable to resolve the profile reference ''{0}''
+Reference_REF_Format1 = Relative URLs must be of the format [ResourceName]/[id], or a search URL is allowed ([type]?parameters. Encountered {0})
+Reference_REF_Format2 = Relative URLs must be of the format [ResourceName]/[id]. Encountered {0}
+Reference_REF_MultipleMatches = Found multiple matching profiles for {0} among choices: {1}
+Reference_REF_NoDisplay = A Reference without an actual reference or identifier should have a display
+Reference_REF_NotFound_Bundle = Bundled or contained reference not found within the bundle/resource {0}
+Reference_REF_NoType = Unable to determine type of target resource
+REFERENCE_REF_QUERY_INVALID = The query part of the conditional reference is not a valid query string ({0})
+REFERENCE_REF_REL_UNSOLVEABLE = The URL ''{0}'' cannot be resolved unless the fullURL is a RESTFul base URL, or a baseURL has been provided and the Bundle is a batch or transaction
+Reference_REF_ResourceType = Matching reference for reference {0} has resourceType {1}
+REFERENCE_REF_SUSPICIOUS = The syntax of the reference ''{0}'' looks incorrect, and it should be checked
+Reference_REF_WrongTarget = The type ''{0}'' is not a valid Target for this element (must be one of {1})
+REFERENCE_REF_WRONGTARGET_LOAD = The type ''{2}'' is not a valid Target for the element {0} (must be {1})
+REFERENCE_RESOLUTION_FAILED = Fetching ''{0}'' failed. System details: {1}: {2}
+reference_to__cannot_be_resolved = reference to {0} cannot be resolved
+REQUEST_TOO_COSTLY_TIME = Request took too long to process (>{0}sec)
+RESOURCE_DUPLICATE_CONTAINED_ID = Duplicate ID for contained resource: {0}
+RESOURCE_MATCHETYPE_DISALLOWED = This resource is not allowed to be a matchetype resource (extension http://hl7.org/fhir/tools/StructureDefinition/matchetype is true)
+RESOURCE_MATCHETYPE_REQUIRED = This resource is required to be a matchetype resource (extension http://hl7.org/fhir/tools/StructureDefinition/matchetype must be true)
+RESOURCE_MATCHETYPE_SUSPECT_TYPE = The type ''{0}'' does not appear to match the matchetype pattern value ''{1}''
+RESOURCE_MATCHETYPE_UNKNOWN_PATTERN = The matchetype pattern value ''{1}'' is not valid
+RESOURCE_NOT_MATCHETYPE_EXTENSION = This resource is not a matcehtype, so it cannot have the extension {0}
+Resource_RES_ID_Malformed_Chars = Invalid Resource id: Invalid Characters (''{0}'')
+Resource_RES_ID_Malformed_Length = Invalid Resource id: Too long ({0} chars)
+Resource_RES_ID_Missing = Resource requires an id, but none is present
+Resource_RES_ID_Prohibited = Resource has an id, but none is allowed
+Resource_resolution_services_not_provided = Resource resolution services not provided
+Resource_type_mismatch_for___ = Resource type mismatch for {0} / {1}
+RESOURCETYPE_PROPERTY_WRONG_TYPE = The JSON element ''resourceType'' has the wrong JSON type: {0}
+Same_id_on_multiple_elements__in_ = Same id ''{0}'' on multiple elements {1}/{2} in {3}
+SCT_NO_MRCM = Not validated against the Machine Readable Concept Model (MRCM)
+SD_BASE_EXPERIMENTAL = The definition builds on ''{0}'' which is experimental, but this definition is not labeled as experimental
+SD_CONSTRAINED_KIND_NO_MATCH = The kind {0} must be the same as the kind {1} in the base structure {3} (base type = {2})
+SD_CONSTRAINED_TYPE_NO_MATCH = The type {0} must be the same as the type in the base structure {1} that is being constrained
+SD_CONTEXT_SHOULD_NOT_BE_ELEMENT = Review the extension type for {1}: extensions should not have a context of {0} unless it''s really intended that they can be used anywhere
+SD_CONTEXT_SHOULD_NOT_BE_FHIRPATH = Review the extension type for {1}: the context of {0} appears to be a simple element, so the context type should be ''element'' not ''fhirpath''
+SD_DERIVATION_KIND_MISMATCH = The structure definition constrains a kind of {0}, but has a different kind ({1})
+SD_DERIVATION_NO_CONCRETE = {0} is labeled as an abstract type, but no concrete descendants were found (check definitions - this is usually an error unless concrete definitions are in some other package)
+SD_ED_ADDITIONAL_BINDING_USAGE_INVALID_ELEMENT = The Usage Context {0}#{1} is a reference to an element that does not exist
+SD_ED_ADDITIONAL_BINDING_USAGE_INVALID_TYPE = The Usage Context value must be of type {1} not {0}
+SD_ED_ADDITIONAL_BINDING_USAGE_UNKNOWN = The Usage Context {0}#{1} is not recognized so cannot be validated
+SD_ED_BIND_MULTIPLE_TYPES = The element {0} has a binding, and has multiple types subject to bindings ({1}). The binding will apply to all the types
+SD_ED_BIND_NO_BINDABLE = The element {0} has a binding, but no bindable types are present {1}
+SD_ED_BIND_NOT_VS = The valueSet reference {1} on element {0} points to something that is not a value set ({2})
+SD_ED_BIND_UNKNOWN_VS = The valueSet reference {1} on element {0} could not be resolved
+SD_ED_EXPERIMENTAL_BINDING = The definition for the element ''{0}'' binds to the value set ''{1}'' which is experimental, but this structure is not labeled as experimental
+SD_ED_SHOULD_BIND = The element {0} has a type that should have a binding ({1}), but no binding is present
+SD_ED_SHOULD_BIND_WITH_VS = The element {0} has a type that should have a binding ({1}), but the binding has no value set
+SD_ED_TYPE_NO_TARGET_PROFILE = Type {0} does not allow for target Profiles
+SD_ED_TYPE_PROFILE_IS_MODIFIER = Profile {0} is for not for a modifier extension, but the {3} element is a modifier
+SD_ED_TYPE_PROFILE_NOT_MODIFIER = Profile {0} is for a modifier extension, but the {3} element is not a modifier
+SD_ED_TYPE_PROFILE_NOTYPE = Found profile {0}, but unable to determine the type it applies to
+SD_ED_TYPE_PROFILE_UNKNOWN = Unable to resolve profile {0}
+SD_ED_TYPE_PROFILE_WRONG = Profile {0} is for type {1}, but the {3} element has type {2}
+SD_ED_TYPE_PROFILE_WRONG_TARGET = Profile {0} is for type {1}, which is not a {4} (which is required because the {3} element has the type {2})
+SD_ED_TYPE_PROFILE_WRONG_TYPE_one = The type {0} is not in the list of allowed type {1} in the profile {2}
+SD_ED_TYPE_PROFILE_WRONG_TYPE_other = The type {0} is not in the list of allowed types {1} in the profile {2}
+SD_ELEMENT_FIXED_WRONG_TYPE = The base element has a fixed type of ''{0}'', so this element must have a fixed value of the same type, not ''{1}''
+SD_ELEMENT_NOT_IN_CONSTRAINT = The element definition for {1} has a property {0} which is not allowed in a profile
+SD_ELEMENT_PATTERN_NO_FIXED = The base element has a pattern type of ''{0}'', so this element must have a fixed value but it doesn''t
+SD_ELEMENT_PATTERN_WRONG_TYPE = The base element has a pattern type of ''{0}'', so this element must have a fixed value of the same type, not ''{1}''
+SD_ELEMENT_REASON_DERIVED = , because the value must match the fixed value define in ''{0}''
+SD_EXTENSION_COMPLIES_WITH_ERROR = This profile does not comply with claimed profile ''{0}''
+SD_EXTENSION_COMPLIES_WITH_UNKNOWN = The profile ''{0}'' cannot be found, so the validator cannot check that the profile does comply with it
+SD_EXTENSION_COMPLIES_WITH_WARNING = The validator cannot confirm that this profile complies with the claimed profile ''{0}''
+SD_EXTENSION_URL_MISMATCH = The fixed value for the extension URL is {1} which doesn''t match the canonical URL {0}
+SD_EXTENSION_URL_MISSING = The value of Extension.url is not fixed to the extension URL {0}
+SD_ILLEGAL_CHARACTERISTICS = This element has a {0} but the types {1} do not make this kind of constraint relevant
+SD_MUST_HAVE_DERIVATION = StructureDefinition {0} must have a derivation, since it has a baseDefinition
+SD_NESTED_MUST_SUPPORT_DIFF = The element {0} has types/profiles/targets that are marked as must support, but the element itself is not marked as must-support. The inner must-supports will be ignored unless the element inherits must-support = true
+SD_NESTED_MUST_SUPPORT_SNAPSHOT = The element {0} has types/profiles/targets that are marked as must support, but the element itself is not marked as must-support
+SD_NO_CONTEXT_INV_WHEN_NOT_EXTENSION = The type is {0} so an extension context invariants should not be specified
+SD_NO_CONTEXT_WHEN_NOT_EXTENSION = The type is {0} so an extension context should not be specified
+SD_NO_SLICING_ON_ROOT = Slicing is not allowed at the root of a profile
+SD_NO_TYPE_CODE_ON_CODE = Snapshot for {1} element {0} has type.code without a value
+SD_NO_TYPES_OR_CONTENTREF = The element {0} has no assigned types, and no content reference
+SD_OBGLIGATION_INHERITS_PROFILE_NO_TARGET = Unable to read a value from this extension
+SD_OBGLIGATION_INHERITS_PROFILE_NOT_RIGHT_BASE = The profile ''{0}'' has a different base ''{1}'' from that expected ''{2}''
+SD_OBGLIGATION_INHERITS_PROFILE_NOT_RIGHT_TYPE = The profile ''{0}'' is not marked as an obligation profile
+SD_OBGLIGATION_INHERITS_PROFILE_TARGET_NOT_FOUND = The profile ''{0}'' could not be found
+SD_OBGLIGATION_PROFILE_DERIVATION = Only profiles that constrain another profile can be marked as an obligation profile
+SD_OBGLIGATION_PROFILE_ILLEGAL = The element ''{0}'' has a property ''{1}'' which is not allowed in Obligation profiles
+SD_OBGLIGATION_PROFILE_ILLEGAL_BINDING = The element ''{0}'' has a binding when the base element does not, and this is not allowed in Obligation profiles
+SD_OBGLIGATION_PROFILE_ILLEGAL_ON_BINDING = The element ''{0}'' has a binding property ''{1}'' which is not allowed in Obligation profiles
+SD_OBGLIGATION_PROFILE_INVALID_BINDING_CODE = The element ''{0}'' has an additional binding purpose of ''{1}'' which is not allowed in Obligation profiles
+SD_OBGLIGATION_PROFILE_INVALID_BINDING_STRENGTH =The element ''{0}'' has a different binding strength (''{1}'') from the base (''{2}'') which is not allowed in Obligation profiles
+SD_OBGLIGATION_PROFILE_PATH_WRONG = The element ''{0}'' path value of ''{1}'' doesn''t match the base path ''{2}''
+SD_OBGLIGATION_PROFILE_UKNOWN = The profile is marked as an obligation profile, but its correctness cannot be checked since the base profile ''{0}'' is not known
+SD_OBGLIGATION_PROFILE_UNMATCHED = The element ''{0}'' has no equivalent in the profile ''{1}'' on which this Obligation Profile is based
+SD_PATH_ERROR = The discriminator path ''{0}'' does not appear to be valid for the element that is being sliced ''{1}'': {2}
+SD_PATH_NO_SLICING = Slicing is not allowed at ''{0}''
+SD_PATH_NOT_VALID = The discriminator path ''{0}'' does not appear to be valid for the element that is being sliced ''{1}''
+SD_PATH_SLICE_INCONSISTENT_MS = The slice ''{0}'' on path ''{1}'' is not marked as ''must-support'' which is not consistent with the element that defines the slicing, where ''must-support'' is true
+SD_PATH_SLICE_INCONSISTENT_TYPE = The slice ''{0}'' on path ''{1}'' has type ''{2}  which is not consistent with the element that defines the slicing, which has the type(s) ''{3}''
+SD_PATH_SLICING_DEPRECATED = The discriminator type ''{0}'' 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)
+SD_PATH_SLICING_DEPRECATED_R5 = The discriminator type ''{0}'' has been deprecated. Use type=value with a pattern[x] instead (if this is not an inherited slicing)
+SD_PATH_TYPE_MISMATCH = The path {1} must start with the type of the structure {0}
+SD_SPECIALIZED_TYPE_MATCHES = The type {0} must not be the same as the type in the base structure {1} that is being specialised
+SD_TABLE_PROHIBITED = The element {0} is prohibited on the element {1} in the context of a {2}
+SD_TABLE_REQUIRED = The element {0} is required on the element {1} in the context of a {2}
+SD_TYPE_MISSING = No type found
+SD_TYPE_NOT_DERIVED = The type {0} can only be used as a type when constraining the base definition of the type
+SD_TYPE_NOT_LOCAL = The type {0} is not legal because it is not defined in the FHIR specification. Other types must have a namespace on them
+SD_TYPE_NOT_LOGICAL = The type {0} can only be defined if the kind is ''logical'' not {1}
+SD_TYPE_NOT_MATCH_NS = The type namespace {0} SHOULD match the url namespace {1} for the definition of the type
+SD_TYPE_PARAM_NOT_SPECIFIED = The type ''{0}'' at {3} is a reference to ''{1}'' which needs a type parameter ''{2}'' but a type parameter is not provided for ''{2}''
+SD_TYPE_PARAMETER_ABSTRACT_WARNING = The type ''{0}'' at {3} refers to the abstract type ''{1}'' but the context is not an abstract type - this is usually an error
+SD_TYPE_PARAMETER_INVALID = The type definition ''{2}'' has a type parameter ''{3}'', which is not consistent with its ancestor type definition ''{0}'' which has the type parameter ''{1}''
+SD_TYPE_PARAMETER_INVALID_REF = The type ''{0}'' is a reference to ''{1}'' which has a type parameter ''{2}'' with a base type of {3} but the type parameter provided is ''{4}'' which is not the right type
+SD_TYPE_PARAMETER_MISSING = The type definition ''{2}'' does not declare a type parameter, but it is derived from the type definition ''{0}'' which has the type parameter ''{1}''
+SD_TYPE_PARAMETER_UNKNOWN = The type definition ''{0}'' has the type parameter ''{1}'' but it is not a known type so derivation consistency cannot be checked
+SD_VALUE_COMPLEX_FIXED = For the complex type {0}, consider using a pattern rather than a fixed value to avoid over-constraining the instance
+SD_VALUE_TYPE_IILEGAL = The element {0} has a {1} of type {2}, which is not in the list of allowed types ({3})
+SD_VALUE_TYPE_REPEAT_HINT = The repeating element has a {1}. The {1} will apply to all the repeats (this has not been clear to all users)
+SD_VALUE_TYPE_REPEAT_WARNING_DOTNET = The repeating element has a {1} value for a primitive type. The DotNet validator will not apply this to all the repeats - this is an error
+SEARCHPARAMETER_BAD_CHAR = The Search Parameter code includes ''{0}'' which has special meaning in the RESTful API, and so this will be a problem
+SEARCHPARAMETER_BASE_WRONG = The resource type {1} is not listed as a base in the SearchParameter this is derived from ({0})
+SEARCHPARAMETER_EXP_WRONG = The expression ''{2}'' is not compatible with the expression ''{1}'' in the derivedFrom SearchParameter {0}, and this likely indicates that the derivation relationship is not valid
+SEARCHPARAMETER_MISSING_COMPONENTS = When the SearchParameter has a type of ''composite'', then the SearchParameter must define two or more components
+SEARCHPARAMETER_NOTFOUND = Unable to find the base Search Parameter {0} so can''t check that this SearchParameter is a proper derivation from it
+SEARCHPARAMETER_TYPE_WRONG = The type {1} is different to the type {0} in the derivedFrom SearchParameter
+SECURITY_STRING_CONTENT_ERROR = The string value contains text that looks like embedded HTML tags, which are not allowed for security reasons in this context
+SECURITY_STRING_CONTENT_WARNING = The string value contains text that looks like embedded HTML tags. If this content is rendered to HTML without appropriate post-processing, it may be a security risk
+Slice_encountered_midway_through_set_path___id___ = Slice encountered midway through set (path = {0}, id = {1}); {2}
+SLICING_CANNOT_BE_EVALUATED = Slicing cannot be evaluated: {0}
+Slicing_rules_on_differential__do_not_match_those_on_base___disciminator___ = Slicing rules on differential ({0}) do not match those on base ({1}) - discriminator @ {2} ({3})
+Slicing_rules_on_differential__do_not_match_those_on_base___order___ = Slicing rules on differential ({0}) do not match those on base ({1}) - order @ {2} ({3})
+Slicing_rules_on_differential__do_not_match_those_on_base___rule___ = Slicing rules on differential ({0}) do not match those on base ({1}) - rule @ {2} ({3})
+SM_DEPENDENT_PARAM_MODE_MISMATCH = The parameter {0} refers to the variable {1} but its mode is {2} which is not the same as the mode required for the group {3}
+SM_DEPENDENT_PARAM_NOT_FOUND = The {1} parameter ''{0}'' was not found. Known variables: {2}
+SM_DEPENDENT_PARAM_TYPE_MISMATCH = The parameter ''{0}'' refers to the variable ''{1}'' but its type is ''{2}'' which is not compatible with the type required for the group ''{3}'', which is ''{4}'' (from map ''{5}'')
+SM_DEPENDENT_PARAM_TYPE_MISMATCH_DUPLICATE = The group {0} has already been used with different parameters, so the type checking may be incorrect (other = [{1}]; this = [{2}])
+SM_GROUP_INPUT_DUPLICATE = The name {0} is already used
+SM_GROUP_INPUT_MODE_INVALID = The group parameter {0} mode {1} isn''t valid
+SM_GROUP_INPUT_MODE_MISMATCH = The type ''{0}'' has mode ''{1}'' which doesn''t match the structure definition mode of ''{2}''
+SM_GROUP_INPUT_NO_TYPE = Group {1} parameter {0} has no type, so the paths cannot be validated
+SM_GROUP_INPUT_TYPE_NOT_DECLARED = The type {0} is not declared and is unknown
+SM_GROUP_INPUT_TYPE_UNKNOWN_STRUCTURE = The type {0} which maps to the canonical URL {1} is not known, so the paths cannot be validated
+SM_GROUP_INPUT_TYPE_UNKNOWN_TYPE = The type {0} is not known, so the paths cannot be validated
+SM_GROUP_NAME_DUPLICATE = The Group name ''{0}'' is already used
+SM_IMPORT_NOT_FOUND = No maps were found to match {0} - validation may be wrong
+SM_LIST_RULE_ID_ONLY_WHEN_SHARE = A ruleId should only be provided when the rule mode is ''share''
+SM_MATCHING_RULEGROUP_NOT_FOUND = Unable to find a default rule for the type pair source={0} and target={1}
+SM_NAME_INVALID = The name {0} is not valid
+SM_NO_LIST_MODE_NEEDED = A list mode should not be provided since this is a rule that can only be executed once
+SM_NO_LIST_RULE_ID_NEEDED = A list ruleId should not be provided since this is a rule that can only be executed once
+SM_ORPHAN_GROUP = The group {0} is not called successfully from within this mapping script, and does not have types on its inputs, so type verification is not possible
+SM_RULE_SOURCE_MAX_REDUNDANT = The max value of {0} is redundant since the valid max is {0}
+SM_RULE_SOURCE_MIN_REDUNDANT = The min value of {0} is redundant since the valid min is {0}
+SM_RULE_SOURCE_UNASSIGNED = The source statement doesn''t assign a variable to the source - check that this is what is intended
+SM_RULEGROUP_NOT_FOUND = The group {0} could not be resolved
+SM_RULEGROUP_PARAM_COUNT_MISMATCH = The group {0} is invoked using {1} parameters, but it actually takes {2} instead
+SM_SOURCE_CONTEXT_UNKNOWN = The source context {0} is not known at this point
+SM_SOURCE_PATH_INVALID = The source path {0}.{1} refers to the path {2} which is unknown
+SM_SOURCE_TYPE_INVALID = The type {0} is not valid in the source context {1}. The possible types are [{2}]
+SM_SOURCE_TYPE_NOT_FOUND = No source type was found, so the default group for this implied dependent rule could not be determined
+SM_TARGET_CONTEXT_UNKNOWN = The target context ''{0}'' is not known at this point
+SM_TARGET_NO_TRANSFORM_NO_CHECKED = When there is no transform, parameters can''t be provided
+SM_TARGET_PATH_INVALID = The target path {0}.{1} refers to the path {2} which is unknown
+SM_TARGET_PATH_MULTIPLE_MATCHES = The target path {0}.{1} refers to the path {2} which could be a reference to multiple elements ({3}). No further checking can be performed
+SM_TARGET_TRANSFORM_EXPRESSION_ERROR = The FHIRPath expression passed as the evaluate parameter is invalid: {0}
+SM_TARGET_TRANSFORM_MISSING_PARAMS = One or more parameters to the translate operation are missing (should be 3, was {0})
+SM_TARGET_TRANSFORM_NOT_CHECKED = Transform {0} not checked yet
+SM_TARGET_TRANSFORM_OP_INVALID_TYPE = The {1} variable {0} type {2} is invalid - must be a primitive
+SM_TARGET_TRANSFORM_OP_UNKNOWN_SOURCE = The {1} variable {2} is unknown for the transform {0}
+SM_TARGET_TRANSFORM_PARAM_COUNT_RANGE = Transform {0} takes {1}-{2} parameter(s) but {3} were found
+SM_TARGET_TRANSFORM_PARAM_COUNT_SINGLE = Transform {0} takes {1} parameter(s) but {2} were found
+SM_TARGET_TRANSFORM_PARAM_UNPROCESSIBLE = The parameter at index {0} could not be processed (type = {1})
+SM_TARGET_TRANSFORM_TRANSLATE_CM_BAD_MODE = The value ''{0}'' for the output parameter is incorrect
+SM_TARGET_TRANSFORM_TRANSLATE_CM_NOT_FOUND = The map_uri ''{0}'' could not be resolved, so the map can''t be checked
+SM_TARGET_TRANSFORM_TRANSLATE_NO_PARAM = No value for the {0} parameter found
+SM_TARGET_TRANSFORM_TRANSLATE_UNKNOWN_SOURCE = The source variable {0} is unknown
+SM_TARGET_TRANSFORM_TYPE_UNKNOWN = The type ''{0}'' is not known
+SM_TARGET_TRANSFORM_TYPE_UNPROCESSIBLE = The value of the type parameter for {0} could not be processed
+SM_TARGET_TRANSLATE_BINDING_SOURCE = The source variable does not have a required binding, so this concept map can''t be checked
+SM_TARGET_TRANSLATE_BINDING_SOURCE_UNMAPPED = The source value set includes one or more codes that the map does not translate: {0}
+SM_TARGET_TRANSLATE_BINDING_TARGET = The target variable does not have a required binding, so this concept map can''t be checked
+SM_TARGET_TRANSLATE_BINDING_TARGET_WRONG = The map produces one or more codes that the target value set does not include: {0}
+SM_TARGET_TRANSLATE_BINDING_VS_SOURCE = The source variable refers to an unknown value set ''{0}'', so this concept map can''t be checked
+SM_TARGET_TRANSLATE_BINDING_VS_TARGET = The target variable refers to an unknown value set ''{0}'', so this concept map can''t be checked
+SM_TARGET_TRANSLATE_BINDING_VSE_SOURCE = There was an error expanding the source value set, so this concept map can''t be checked: ''{0}''
+SM_TARGET_TRANSLATE_BINDING_VSE_TARGET = There was an error expanding the target value set, so this concept map can''t be checked: ''{0}''
+SM_TARGET_TYPE_MULTIPLE_POSSIBLE = Multiple types are possible here ({0}) so further type checking is not possible
+SM_TARGET_TYPE_NOT_FOUND = No target type was found, so the default group for this implied dependent rule could not be determined
+SM_TARGET_TYPE_UNKNOWN = The type of the target variable is not known: {0}
+SNAPSHOT_EXISTING_PROBLEM = The generated snapshot has a different number of elements {1} than the originally provided snapshot {0}
+SNAPSHOT_IS_EMPTY = The snapshot for the profile ''{0}'' is empty. This is usually due to a processing error logged elsewhere
+#STATUS_CODE_HINT = The code is {0}
+#STATUS_CODE_HINT_CODE = The code ''{1}'' is {0}
+#STATUS_CODE_WARNING = The code is valid but is {0}
+STATUS_CODE_WARNING_CODE = The concept ''{1}'' is valid but is {0}
+StructureDefinition__at__illegal_constrained_type__from__in_ = StructureDefinition {0} at {1}: invalid constrained type {2} from {3} in {4}
+Terminology_PassThrough_TX_Message = {0} (for ''{1}#{2}'')
+Terminology_TX_Binding_CantCheck = Binding by URI reference cannot be checked
+Terminology_TX_Binding_Missing = Binding for CodeableConcept {0} missing 
+Terminology_TX_Binding_Missing2 = Binding for Coding {0} missing
+Terminology_TX_Binding_NoServer = The value provided ([{0}]) could not be validated in the absence of a terminology server
+Terminology_TX_Binding_NoSource = Binding for path {0} in profile {1} has no source, so can''t be checked
+Terminology_TX_Code_ValueSet = No code provided, and a code is required from the value set {0}
+Terminology_TX_Code_ValueSet_Ext = No code provided, and a code should be provided from the value set {0}
+Terminology_TX_Code_ValueSet_MISSING = No code provided, and a code is required from the value set
+Terminology_TX_Code_ValueSetMax = No code provided, and a code must be provided from the value set {0} (max value set {1})
+Terminology_TX_Coding_Count = Expected {0} but found {1} coding elements
+Terminology_TX_Confirm_1_CC = Could not confirm that the codings provided are in the value set {0} and a coding from this value set is required (class = {1})
+Terminology_TX_Confirm_2_CC = Could not confirm that the codings provided are in the value set {0} and a coding should come from this value set unless it has no suitable code (the validator cannot judge what is suitable) (class = {1})
+Terminology_TX_Confirm_3_CC = Could not confirm that the codings provided are in the value set {0} and a coding is recommended to come from this value set (class = {1})
+Terminology_TX_Confirm_4a = The code provided ({2}) was not found in the value set {0}, and a code from this value set is required: {1}
+Terminology_TX_Confirm_5 = The code provided ({1}) is not in the value set {0}, and a code should come from this value set unless it has no suitable code (the validator cannot judge what is suitable)
+Terminology_TX_Confirm_6 = The code provided ({1}) is not in the value set {0}, and a code is recommended to come from this value set
+Terminology_TX_Display_Wrong = Display should be ''{0}''
+Terminology_TX_Error_CodeableConcept = Error {0} validating CodeableConcept
+Terminology_TX_Error_CodeableConcept_Max = Error {0} validating CodeableConcept using maxValueSet
+Terminology_TX_Error_Coding1 = Error {0} validating Coding
+Terminology_TX_Error_Coding2 = Error {0} validating Coding: {1}
+TERMINOLOGY_TX_HINT = {1}
+TERMINOLOGY_TX_NOSVC_BOUND_EXT = Could not confirm that the codes provided are from the extensible value set {0} because there is no terminology service
+TERMINOLOGY_TX_NOSVC_BOUND_REQ = Could not confirm that the codes provided are from the required value set {0} because there is no terminology service
+Terminology_TX_NoValid_1_CC = None of the codings provided are in the value set {0}, and a coding from this value set is required) (codes = {1})
+Terminology_TX_NoValid_10 = The code provided is not in the maximum value set {0}, and a code from this value set is required) (code = {1}#{2})
+Terminology_TX_NoValid_11 = The code provided is not in the maximum value set {0}, and a code from this value set is required) (code = {1}#{2}), error = {3})
+Terminology_TX_NoValid_12 = The Coding provided ({2}) was not found in the value set {0}, and a code is required from this value set. {1}
+Terminology_TX_NoValid_13 = The Coding provided ({2}) was not found in the value set {0}, and a code should come from this value set unless it has no suitable code (note that the validator cannot judge what is suitable). {1}
+Terminology_TX_NoValid_14 = The Coding provided ({2}) was not found in the value set {0}, and a code is recommended to come from this value set. {1}
+Terminology_TX_NoValid_15 = The value provided (''{0}'') could not be validated in the absence of a terminology server
+Terminology_TX_NoValid_16 = The value provided (''{0}'') was not found in the value set {1}, and a code is required from this value set {2}
+Terminology_TX_NoValid_17 = The value provided (''{0}'') was not found in the value set {1}, and a code should come from this value set unless it has no suitable code (note that the validator cannot judge what is suitable) {2}
+Terminology_TX_NoValid_18 = The value provided (''{0}'') was not found in the value set {1}, and a code is recommended to come from this value set{2}
+Terminology_TX_NoValid_2_CC = None of the codings provided are in the value set {0}, and a coding should come from this value set unless it has no suitable code (note that the validator cannot judge what is suitable) (codes = {1})
+Terminology_TX_NoValid_3_CC = None of the codings provided are in the value set {0}, and a coding is recommended to come from this value set (codes = {1})
+Terminology_TX_NoValid_4 = The Coding provided ({2}) was not found in the value set {0}, and a code is required from this value set {1}
+Terminology_TX_NoValid_5 = The Coding provided ({2}) was not found in the value set {0}, and a code should come from this value set unless it has no suitable code (the validator cannot judge what is suitable) {1}
+Terminology_TX_NoValid_6 = The Coding provided ({2}) was not found in the value set {0}, and a code is recommended to come from this value set {1}
+Terminology_TX_NoValid_7 = None of the codes provided could be validated against the maximum value set {0}, (error = {2})
+Terminology_TX_NoValid_8 = None of the codes provided are in the maximum value set {0}, and a code from this value set is required) (codes = {1})
+Terminology_TX_NoValid_9 = The code provided ({2}) could not be validated against the maximum value set {0}, (error = {1})
+TERMINOLOGY_TX_OID_MULTIPLE_MATCHES = The OID ''{0}'' matches multiple resources ({1})
+TERMINOLOGY_TX_OID_MULTIPLE_MATCHES_CHOSEN = The OID ''{0}'' matches multiple resources ({2}); {1} was chosen as the most appropriate
+TERMINOLOGY_TX_SYSTEM_HTTPS = The system URL ''{0}'' wrongly starts with https: not http:
+Terminology_TX_System_Invalid = Invalid System URI: {0}
+TERMINOLOGY_TX_SYSTEM_NO_CODE = A code with no system has no defined meaning, and it cannot be validated. A system should be provided
+TERMINOLOGY_TX_SYSTEM_NOT_USABLE = The definition for the Code System with URI ''{0}'' doesn''t provide any codes so the code cannot be validated
+Terminology_TX_System_Relative = Coding.system must be an absolute reference, not a local reference
+Terminology_TX_System_Unknown = Unknown Code System ''{0}''
+Terminology_TX_System_ValueSet = Invalid System URI: {0} - cannot use a value set URI as a system
+Terminology_TX_System_ValueSet2 = The Coding references a value set, not a code system (''{0}'')
+TERMINOLOGY_TX_SYSTEM_WRONG_BUILD = The code system reference {0} is wrong - the code system reference cannot be a reference to build.fhir.org. This may be the correct reference: {1}
+TERMINOLOGY_TX_SYSTEM_WRONG_HTML = The code system reference {0} is wrong - the code system reference cannot be to an HTML page. This may be the correct reference: {1}
+TERMINOLOGY_TX_UNKNOWN_OID = The OID ''{0}'' is not known, so the code can''t be validated
+Terminology_TX_ValueSet_NotFound = ValueSet ''{0}'' not found
+Terminology_TX_ValueSet_NotFound_CS = Found a reference to a CodeSystem ''{0}'' where a ValueSet belongs
+TERMINOLOGY_TX_WARNING = {1}
+Text_should_not_be_present = Text should not be present (''{0}'')
+The_base_snapshot_marks_a_slicing_as_closed_but_the_differential_tries_to_extend_it_in__at__ = The base snapshot marks a slicing as closed, but the differential tries to extend it in {0} at {1} ({2})
+This__cannot_be_parsed_as_a_FHIR_object_no_namespace = This ''{0}'' cannot be parsed (no namespace on the XML Root element)
+This_base_property_must_be_an_Array_not_ = This base property must be an Array, not {0}
+This_cannot_be_parsed_as_a_FHIR_object_no_name = This content cannot be parsed (no name)
+This_does_not_appear_to_be_a_FHIR_resource_unknown_name_ = This content cannot be parsed (unknown or unrecognized resource name ''{0}'')
+This_does_not_appear_to_be_a_FHIR_resource_unknown_namespacename_ = This content cannot be parsed (unknown or unrecognized XML Root element namespace/name ''{0}::{1}'')
+This_element_does_not_match_any_known_slice_ = This element does not match any known slice {0} (this may not be a problem, but you should check that it''s not intended to match a slice)
+This_property_must_be__not_ = The property {2} must be {0}, not {1} (at {3})
+This_property_must_be_a_Literal_not_ = This property must be a Literal, not {0}
+This_property_must_be_a_URI_or_bnode_not_ = This property must be a URI or bnode, not {0}
+This_property_must_be_an_Array_not_ = The property {1} must be a JSON Array, not {0} (at {2})
+This_property_must_be_an_object_not_ = This property must be an object, not {0} ({1} at {2})
+This_property_must_be_an_simple_value_not_ = This property must be a simple value, not {0} ({1} at {2})
+TX_GENERAL_CC_ERROR_MESSAGE = No valid coding was found for the value set ''{0}''
+TX_SERVER_NO_BATCH_RESPONSE = The server return null from a batch validation request
+TX_SERVER_NOT_READY = The full data set is only {0}% loaded ({1} of {2}) for searching - repeat this query in a few minutes (max ~15min);
+TYPE_CHECKS_FIXED_CC = The fixed value [system {0}, code {1}, and display ''{2}''] defined in the profile {3} not found. Issues: {4}
+TYPE_CHECKS_FIXED_CC_US = The fixed value [system {0}, code {1}, display ''{2}'' and userSelected {5}] defined in the profile {3} not found. Issues: {4}
+TYPE_CHECKS_PATTERN_CC = The pattern [system {0}, code {1}, and display ''{2}''] defined in the profile {3} not found. Issues: {4}
+TYPE_CHECKS_PATTERN_CC_US = The pattern [system {0}, code {1}, display ''{2}'' and userSelected {5}] defined in the profile {3} not found. Issues: {4}
+type_on_first_differential_element = Type on first differential element!
+type_on_first_snapshot_element_for__in__from_ = Type on first snapshot element for {0} in {1} from {2}
+TYPE_SPECIFIC_CHECKS_CANONICAL_ABSOLUTE = Canonical URLs must be absolute URLs if they are not fragment references ({0})
+TYPE_SPECIFIC_CHECKS_CANONICAL_CONTAINED = Canonical URLs in contained resources must be absolute URLs if present ({0})
+TYPE_SPECIFIC_CHECKS_DT_ATT_NO_CONTENT = Attachments have data and/or url, or else SHOULD have either contentType and/or language
+TYPE_SPECIFIC_CHECKS_DT_ATT_NO_FETCHER = Attachment size cannot be checked because the validator has not been set up to access the network (url = {0})
+TYPE_SPECIFIC_CHECKS_DT_ATT_SIZE_CORRECT = Stated Attachment Size {0} does not match actual attachment size {1}
+TYPE_SPECIFIC_CHECKS_DT_ATT_SIZE_INVALID = Stated Attachment Size {0} is not valid
+TYPE_SPECIFIC_CHECKS_DT_ATT_TOO_LONG = Attachment size is {0} bytes which exceeds the stated limit of {1} bytes
+TYPE_SPECIFIC_CHECKS_DT_ATT_UNKNOWN_URL_SCHEME = Attachment size cannot be checked because the validator doesn''t understand how to access {0}
+TYPE_SPECIFIC_CHECKS_DT_ATT_URL_ERROR = Attachment size cannot be checked because there was an error accesssing {0}: {1}
+TYPE_SPECIFIC_CHECKS_DT_BASE64_NO_WS_ERROR = Base64 encoded values are not allowed to contain any whitespace (per RFC 4648). Note that non-validating readers are encouraged to accept whitespace anyway
+TYPE_SPECIFIC_CHECKS_DT_BASE64_NO_WS_WARNING = Base64 encoded values SHOULD not contain any whitespace (per RFC 4648). Note that non-validating readers are encouraged to accept whitespace anyway
+TYPE_SPECIFIC_CHECKS_DT_BASE64_TOO_LONG = Base64 size is {0} bytes which exceeds the stated limit of {1} bytes
+Type_Specific_Checks_DT_Base64_Valid = The value ''{0}'' is not a valid Base64 value
+Type_Specific_Checks_DT_Boolean_Value = Boolean values must be ''true'' or ''false''
+TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS = There are multiple different potential matches for the url ''{0}''. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version ''{1}'', found versions: {2}. Suggested fix: change the canonical reference from ''{0}'' to ''{0}|{1}''
+TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVE = A definition could not be found for Canonical URL ''{0}''
+TYPE_SPECIFIC_CHECKS_DT_URL_WRONG_HTTPS = A definition could not be found for Canonical URL ''{0}'' but a definition can be found for ''{1}'' - change from https: to http:
+TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVE_NC = Canonical URL ''{0}'' exists, but can''t be loaded, so it can''t be checked for validity
+TYPE_SPECIFIC_CHECKS_DT_CANONICAL_TYPE = Canonical URL ''{0}'' refers to a resource that has the wrong type. Found {1} expecting one of {2}
+Type_Specific_Checks_DT_Code_WS = The code ''{0}'' is not valid (whitespace rules)
+Type_Specific_Checks_DT_Date_Valid = Not a valid date format: ''{0}''
+Type_Specific_Checks_DT_DateTime_Reasonable = The value ''{0}'' is outside the range of reasonable years - check for data entry error
+Type_Specific_Checks_DT_DateTime_Regex = Not a valid instant format: ''{0}''
+Type_Specific_Checks_DT_DateTime_TZ = If a date has a time, it must have a timezone
+Type_Specific_Checks_DT_DateTime_Valid = Not a valid date/time format: ''{0}''
+TYPE_SPECIFIC_CHECKS_DT_DECIMAL_CHARS = Found {0} decimal places which exceeds the stated limit of {1} digits
+Type_Specific_Checks_DT_Decimal_GT = decimal value is greater than permitted maximum value of {0}
+Type_Specific_Checks_DT_Decimal_LT = decimal value is less than permitted minimum value of {0}
+Type_Specific_Checks_DT_Decimal_Range = The value ''{0}'' is outside the range of commonly/reasonably supported decimals
+Type_Specific_Checks_DT_Decimal_Valid = The value ''{0}'' is not a valid decimal
+Type_Specific_Checks_DT_ID_Valid = id value ''{0}'' is not valid
+TYPE_SPECIFIC_CHECKS_DT_IDENTIFIER_IETF_SYSTEM_VALUE = if identifier.system is ''urn:ietf:rfc:3986'', then the identifier.value must be a full URI (e.g. start with a scheme), not ''{0}''
+TYPE_SPECIFIC_CHECKS_DT_IDENTIFIER_IETF_SYSTEM_WRONG_1 = The URL ''https://tools.ietf.org/html/rfc4122'' is not correct for the identifier ''{0}''
+TYPE_SPECIFIC_CHECKS_DT_IDENTIFIER_IETF_SYSTEM_WRONG_2 = The URL ''https://tools.ietf.org/html/rfc4122'' should not be used with the UUID ''{0}''. Prefix the value with ''urn:uuid:'' and use the system value ''urn:ietf:rfc:3986'' instead
+TYPE_SPECIFIC_CHECKS_DT_IDENTIFIER_IETF_SYSTEM_WRONG_3 = The URL ''https://tools.ietf.org/html/rfc4122'' should not be used with the UUID ''{0}''. Use the system value ''urn:ietf:rfc:3986'' instead
+Type_Specific_Checks_DT_Identifier_System = Identifier.system must be an absolute reference, not a local reference
+Type_Specific_Checks_DT_Instant_Valid = Not a valid instant ({0})
+Type_Specific_Checks_DT_Integer_GT = integer value is greater than permitted maximum value of {0}
+Type_Specific_Checks_DT_Integer_LT = integer value is less than permitted minimum value of {0}
+Type_Specific_Checks_DT_Integer_LT0 = value is less than permitted minimum value of 0
+Type_Specific_Checks_DT_Integer_LT1 = value is less than permitted minimum value of 1
+Type_Specific_Checks_DT_Integer_Valid = The value ''{0}'' is not a valid integer
+Type_Specific_Checks_DT_Integer64_Valid = The value ''{0}'' is not a valid integer64
+TYPE_SPECIFIC_CHECKS_DT_MARKDOWN_HTML = The markdown contains content that appears to be an embedded HTML tag starting at ''{0}''. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour
+Type_Specific_Checks_DT_OID_Start = OIDs must start with urn:oid:
+Type_Specific_Checks_DT_OID_Valid = OIDs must be valid ({0})
+Type_Specific_Checks_DT_Primitive_Length = value is longer than permitted maximum length of {0}
+Type_Specific_Checks_DT_Primitive_NotEmpty = value cannot be empty
+Type_Specific_Checks_DT_Primitive_Regex = Element value ''{0}'' does not meet regex ''{1}''
+TYPE_SPECIFIC_CHECKS_DT_PRIMITIVE_REGEX_EXCEPTION = Exception evaluating regex ''{0}'' on type {1}: {2}
+Type_Specific_Checks_DT_Primitive_Regex_Type = Element value ''{0}'' does not meet {1} regex ''{2}''
+TYPE_SPECIFIC_CHECKS_DT_PRIMITIVE_REGEX_TYPE_ALT = Neither the element value ''{0}'' or the formatted value ''{1}'' meet {2} regex ''{3}''
+Type_Specific_Checks_DT_Primitive_ValueExt = Primitive types must have a value or must have child extensions
+Type_Specific_Checks_DT_Primitive_WS = Primitive types should not only be whitespace
+TYPE_SPECIFIC_CHECKS_DT_QTY_MAX_CODE_MISMATCH = The maxValue in the profile has a system code of {0} which is different to the system code in the value {1} so the maximum value cannot be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MAX_MIN_NO_CODE = The maxValue in the profile has no code so the maximum value cannot be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MAX_MIN_NO_CONVERT = Unable to convert value {0} from unit {1} to maxValue unit {2} based on UCUM definitions; maximum value is not valid
+TYPE_SPECIFIC_CHECKS_DT_QTY_MAX_MIN_NO_SYSTEM = The maxValue in the profile has no system so the maximum value cannot be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MAX_MIN_NO_VALUE = The maxValue in the profile doesn''t have an actual value, so the maximum value can''t be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MAX_NO_UCUM_SVC = There is no UCUM service, and the UCUM codes aren''t identical, so the maximum value can''t be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MAX_SYSTEM_MISMATCH = The maxValue in the profile has a system of {0} which is different to the system in the value {1} so the maximum value cannot be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MAX_VALUE_NO_CODE = The value has no code so the maximum value cannot be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MAX_VALUE_NO_SYSTEM = The value has no system so the maximum value cannot be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MAX_VALUE_NO_VALUE = The quantity doesn''t have an actual value, so the maximum value can''t be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MAX_VALUE_WRONG = The value in the instance ({2}) is greater than the specified maximum value ({3})
+TYPE_SPECIFIC_CHECKS_DT_QTY_MAX_VALUE_WRONG_UCUM = The value in the instance ({0} {1}) is greater than the specified maxValue ({2} {3}) after UCUM conversion
+TYPE_SPECIFIC_CHECKS_DT_QTY_MIN_CODE_MISMATCH = The minValue in the profile has a system code of {0} which is different to the system code in the value {1} so the minimum value cannot be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MIN_MIN_NO_CODE = The minValue in the profile has no code so the minimum value cannot be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MIN_MIN_NO_CONVERT = Unable to convert value {0} from unit {1} to minValue unit {2} based on UCUM definitions; minimum value is not valid
+TYPE_SPECIFIC_CHECKS_DT_QTY_MIN_MIN_NO_SYSTEM = The minValue in the profile has no system so the minimum value cannot be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MIN_MIN_NO_VALUE = The minValue in the profile doesn''t have an actual value, so the minimum value can''t be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MIN_NO_UCUM_SVC = There is no UCUM service, and the UCUM codes aren''t identical, so the minimum value can''t be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MIN_SYSTEM_MISMATCH = The minValue in the profile has a system of {0} which is different to the system in the value {1} so the minimum value cannot be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MIN_VALUE_NO_CODE = The value has no code so the minimum value cannot be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MIN_VALUE_NO_SYSTEM = The value has no system so the minimum value cannot be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MIN_VALUE_NO_VALUE = The quantity doesn''t have an actual value, so the minimum value can''t be checked
+TYPE_SPECIFIC_CHECKS_DT_QTY_MIN_VALUE_WRONG = The value in the instance ({2}) is less than the specified minimum value ({3})
+TYPE_SPECIFIC_CHECKS_DT_QTY_MIN_VALUE_WRONG_UCUM = The value in the instance ({0} {1}) is less than the specified minValue ({2} {3}) after UCUM conversion
+TYPE_SPECIFIC_CHECKS_DT_QTY_NO_QTY = Found {0} of type {2} in the profile validating a Quantity (so it must be a Quantity)
+TYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS = UCUM Codes that contain human readable annotations like {0} 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
+TYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS_NO_UNIT = UCUM Codes that contain human readable annotations like {0} 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 
+TYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS_NOT_IN_UNIT = UCUM Codes that contain human readable annotations like {0} 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 ''{1}'' SHOULD contain the annotation (it does not)
+Type_Specific_Checks_DT_String_Length = value is longer than permitted maximum length of 1 MB (1048576 bytes)
+Type_Specific_Checks_DT_String_WS = value should not start or finish with whitespace ''{0}''
+Type_Specific_Checks_DT_String_WS_ALL = value should not be all whitespace ''{0}''
+Type_Specific_Checks_DT_Time_Valid = Not a valid time ({0})
+Type_Specific_Checks_DT_URI_OID = URI values cannot start with oid:
+Type_Specific_Checks_DT_URI_UUID = URI values cannot start with uuid:
+Type_Specific_Checks_DT_URI_WS = URI values cannot have whitespace(''{0}'')
+TYPE_SPECIFIC_CHECKS_DT_URL_EXAMPLE = Example URLs are not allowed in this context ({0})
+Type_Specific_Checks_DT_URL_Resolve = No definition could be found for URL value ''{0}''
+TYPE_SPECIFIC_CHECKS_DT_URL_INTERNAL = The URL value ''{0}'' is invalid because there is no matching target
+TYPE_SPECIFIC_CHECKS_DT_URL_INTERNAL_WARN = The URL value ''{0}'' might be wrong because it appears to point to an internal target, but there is no matching target
+Type_Specific_Checks_DT_UUID_Strat = UUIDs must start with urn:uuid:
+Type_Specific_Checks_DT_UUID_Valid = UUIDs must be valid and lowercase ({0})
+TYPE_SPECIFIC_CHECKS_DT_XHTML_ACTIVE_HREF = Hyperlink scheme ''{3}'' in ''{0}'' at ''{1}'' for ''{2}'' has active content, which is a security risk and not allowed
+TYPE_SPECIFIC_CHECKS_DT_XHTML_EMPTY_HREF = Hyperlink at ''{0}'' for ''{1}'' is empty
+TYPE_SPECIFIC_CHECKS_DT_XHTML_LITERAL_HREF = Hyperlink scheme ''{3}'' in ''{0}'' at ''{1}'' for ''{2}'' is not a valid hyperlinkable scheme
+TYPE_SPECIFIC_CHECKS_DT_XHTML_MULTIPLE_MATCHES = Hyperlink ''{0}'' at ''{1}'' for ''{2}'' resolves to multiple targets ({3})
+Type_Specific_Checks_DT_XHTML_Resolve = Hyperlink ''{0}'' at ''{1}'' for ''{2}'' does not resolve
+Type_Specific_Checks_DT_XHTML_Resolve_Img = Image source ''{0}'' at ''{1}'' does not resolve
+TYPE_SPECIFIC_CHECKS_DT_XHTML_UNKNOWN_HREF = Hyperlink scheme ''{3}'' in ''{0}'' at ''{1}'' for ''{2}'' is not a widely supported protocol and should be checked
+TYPE_SPECIFIER_ABSTRACT_TYPE = The Type specifier {1} specified an abstract type {0}
+TYPE_SPECIFIER_ILLEGAL_TYPE = The Type specifier {1} specified an invalid type {0}
+TYPE_SPECIFIER_NM_ABSTRACT_TYPE = No Type specifier matched, and the underlying type {0} is not abstract
+TYPE_SPECIFIER_NM_ILLEGAL_TYPE = No Type specifier matched, and the underlying type {0} is not valid
+UNABLE_TO_CHECK_IF_THE_PROVIDED_CODES_ARE_IN_THE_VALUE_SET_ = Unable to check whether the code is in the value set ''{0}''
+UNABLE_TO_CHECK_IF_THE_PROVIDED_CODES_ARE_IN_THE_VALUE_SET_CS = Unable to check whether the code is in the value set ''{0}'' because the code system {1} was not found
+UNABLE_TO_CHECK_IF_THE_PROVIDED_CODES_ARE_IN_THE_VALUE_SET_VS = Unable to check whether the code is in the value set ''{0}'' because the value set {1} was not found
+Unable_to_connect_to_terminology_server = Unable to connect to terminology server at {1}. Error = {0}
+Unable_to_connect_to_terminology_server_Use_parameter_tx_na_tun_run_without_using_terminology_services_to_validate_LOINC_SNOMED_ICDX_etc_Error__ = Unable to connect to terminology server at {1}. Use parameter ''-tx n/a'' to run without using terminology services to validate LOINC, SNOMED, ICD-X etc. Error = {0}
+UNABLE_TO_DETERMINE_TYPE_CONTEXT_INV = The types could not be determined from the extension context, so the invariant can''t be validated (types = {0})
+Unable_to_find__resolving_discriminator__from_ = Unable to find {0} resolving discriminator {1} from {2}
+Unable_to_find_base__for_ = Unable to find base {0} for {1}
+Unable_to_find_base_definition_for_logical_model__from_ = Unable to find base definition for logical model: {0} from {1}
+Unable_to_find_element_ = Unable to find element {0}
+Unable_to_find_element__in_ = Unable to find element {0} in {1}
+Unable_to_find_element_with_id_ = Unable to find element with id ''{0}''
+Unable_to_find_profile__at_ = Unable to find profile ''{0}'' at {1}
+Unable_to_find_resource__at__resolving_discriminator__from_ = Unable to find resource {0} at {1} resolving discriminator {2} from {3}
+Unable_to_find_resourceType_property = Unable to find resourceType property
+Unable_to_handle_system__concept_filter_with_op__ = Unable to handle system {0} concept filter with op = {1}
+Unable_to_handle_system__filter_with_property__ = Unable to handle system {0} filter with property = {1}, op = {2}
+UNABLE_TO_HANDLE_SYSTEM__PROPERTY_FILTER_WITH_OP__ = Unable to handle system {0} property filter with op = {1}
+UNABLE_TO_HANDLE_SYSTEM_FILTER_WITH_NO_VALUE = The system {0} filter with property = {1}, op = {2} has no value
+UNABLE_TO_INFER_CODESYSTEM = The System URI could not be determined for the code ''{0}'' in the ValueSet ''{1}''
+Unable_to_locate_the_profile__in_order_to_validate_against_it = Unable to locate the profile ''{0}'' in order to validate against it
+Unable_to_process_request_for_resource_for___ = Unable to process request for resource for {0} / {1}
+Unable_to_resolve_ = Unable to resolve the reference {0}
+Unable_to_resolve_actual_type_ = Unable to resolve actual type {0}
+UNABLE_TO_RESOLVE_CONTENT_REFERENCE_IN_THIS_CONTEXT = Unable to resolve the content reference {0} on element {1} (path = {2}) in this context
+Unable_to_resolve_element__in_profile_ = Unable to resolve element {0} in profile {1}
+Unable_to_resolve_name_reference__at_path_ = Unable to resolve name reference {0} at path {1}
+Unable_to_resolve_profile__in_element_ = Unable to resolve profile {0} in element {1}
+Unable_to_resolve_reference_to_ = Unable to resolve reference to {0}
+Unable_to_resolve_slice_matching__no_fixed_value_or_required_value_set = Unable to resolve slice matching - no fixed value or required value set
+Unable_to_resolve_slice_matching__slice_matching_by_value_set_not_done = Unable to resolve slice matching - slice matching by value set not done
+Unable_to_resolve_system__no_value_set = Unable to resolve system - no value set
+Unable_to_resolve_system__value_set_expansion_has_multiple_systems = The System URI could not be determined for the code ''{0}'' in the ValueSet ''{1}'': value set expansion has multiple systems
+Unable_to_resolve_system__value_set_has_imports = The System URI could not be determined for the code ''{0}'' in the ValueSet ''{1}'': value set has imports
+Unable_to_resolve_system__value_set_has_include_with_filter = The System URI could not be determined for the code ''{0}'' in the ValueSet ''{1}'': include #{2} has a filter on system {3}: {4}
+Unable_to_resolve_system__value_set_has_include_with_no_system = Unable to resolve system - value set {0} include #{1} has no system
+Unable_to_resolve_system__value_set_has_include_with_unknown_system = The System URI could not be determined for the code ''{0}'' in the ValueSet ''{1}'': include #{2} has system {3} which could not be found, and the server returned error {4}
+Unable_to_resolve_system__value_set_has_multiple_matches = The System URI could not be determined for the code ''{0}'' in the ValueSet ''{1}'': value set expansion has multiple matches: {2}
+Unable_to_resolve_system__value_set_has_no_includes_or_expansion = The System URI could not be determined for the code ''{0}'' in the ValueSet ''{1}'': value set has no includes or expansion
+UNABLE_TO_RESOLVE_SYSTEM_SYSTEM_IS_INDETERMINATE = The code system {1} referred to from value set {0} has a grammar, and the code might be valid in it
+Unable_to_resolve_value_Set_ = A definition for the value Set ''{0}'' could not be found
+Unable_to_validate_code_without_using_server = Unable to validate code without using server because: {0}
+Undefined_attribute__on__for_type__properties__ = Undefined attribute ''@{0}'' on {1} for type {2}
+Undefined_element_ = Undefined element ''{0}'' at {1}
+Unexpected_condition_in_differential_typeslicetypelistsize__1_at_ = Unexpected condition in differential: invalid type at {0}/{1}
+Unexpected_condition_in_differential_typeslicetypelistsize__10_and_implicit_slice_name_does_not_contain_a_valid_type__at_ = Unexpected condition in differential: implicit slice name does not contain a valid type (''{0}''?) at {1}/{2}
+Unexpected_datatype_for_rdfstype = Unexpected datatype for rdfs:type
+Unhandled_situation_resource_is_profiled_to_more_than_one_option__cannot_sort_profile = Unhandled situation: resource is profiled to more than one option - cannot sort profile
+UNICODE_BIDI_CONTROLS_CHARS_DISALLOWED = The Unicode sequence has bi-di control characters which are not allowed in this context: {0}
+UNICODE_BIDI_CONTROLS_CHARS_MATCH = The Unicode sequence has unterminated bi-di control characters (see CVE-2021-42574): {0}
+UNICODE_XML_BAD_CHARS_one = This content includes the character {1} (hex value). This character is illegal in the XML version of FHIR, and there is generally no valid use for such characters
+UNICODE_XML_BAD_CHARS_other = This content includes the characters {1} (hex values). These characters are illegal in the XML version of FHIR, and there is generally no valid use for such characters
+Unknown_Code_in = Unknown code ''{0}'' in the CodeSystem ''{1}''
+UNKNOWN_CODE_IN_FRAGMENT = Unknown Code ''{0}'' in the CodeSystem ''{1}'' version ''{2}'' - note that the code system is labeled as a fragment, so the code may be valid in some other fragment
+Unknown_Code_in_Version = Unknown code ''{0}'' in the CodeSystem ''{1}'' version ''{2}''
+Unknown_Code_in_Version_SCT = Unknown code ''{0}'' in the CodeSystem ''{1}'' version ''{2}'' ({3})
+NO_CODE_PROVIDED = No code provided for CodeSystem ''{0}''
+NO_CODE_PROVIDED_VERSION = No code provided for CodeSystem ''{0}'' version ''{1}''
+UNKNOWN_CODESYSTEM = A definition for CodeSystem ''{0}'' could not be found, so the code cannot be validated
+UNKNOWN_CODESYSTEM_VERSION = A definition for CodeSystem ''{0}'' version ''{1}'' could not be found, so the code cannot be validated. Valid versions: {2}
+UNKNOWN_CODESYSTEM_VERSION_NONE = A definition for CodeSystem ''{0}'' version ''{1}'' could not be found, so the code cannot be validated. No versions of this code system are known
+UNKNOWN_CODESYSTEM_EXP = A definition for CodeSystem ''{0}'' could not be found, so the value set cannot be expanded
+UNKNOWN_CODESYSTEM_VERSION_EXP = A definition for CodeSystem ''{0}'' version ''{1}'' could not be found, so the value set cannot be expanded. Valid versions: {2}
+UNKNOWN_CODESYSTEM_VERSION_EXP_NONE = A definition for CodeSystem ''{0}'' version ''{1}'' could not be found, so the value set cannot be expanded. No versions of this code system are known
+Unknown_Data_format_ = Unknown Data format ''{0}''
+Unknown_Date_format_ = Unknown Date format ''{0}''
+UNKNOWN_PROPERTY = Unknown property name {0} in path {1}
+Unknown_resource_type_missing_rdfstype = Unknown resource type (missing rdfs:type)
+Unknown_type__at_ = Unknown type {0} at {1}
+Unrecognised_extension_context_ = Unrecognized extension context {0}
+Unrecognised_predicate_ = Unrecognized predicate ''{0}''
+Unrecognised_property_ = Unrecognized property ''{0}''
+UNRECOGNISED_PROPERTY_TYPE = Invalid JSON type {0} for the element {1}; valid types = {2}
+UNRECOGNISED_PROPERTY_TYPE_WRONG = Invalid type {2} for the element {1}; valid types = {3}, JSON type = {0}
+Unsupported_CodeableConcept_pattern__extensions_are_not_allowed__for_discriminator_for_slice_ = Unsupported CodeableConcept pattern - extensions are not allowed - for discriminator ({0}) for slice {1}
+Unsupported_CodeableConcept_pattern__must_have_at_least_one_coding__for_discriminator_for_slice_ = Unsupported CodeableConcept pattern - must have at least one coding - for discriminator ({0}) for slice {1}
+Unsupported_CodeableConcept_pattern__using_text__for_discriminator_for_slice_ = Unsupported CodeableConcept pattern - using text - for discriminator ({0}) for slice {1}
+Unsupported_fixed_pattern_type_for_discriminator_for_slice__ = Unsupported fixed pattern type for discriminator ({0}) for slice {1}: {2}
+Unsupported_fixed_value_type_for_discriminator_for_slice__ = Unsupported fixed value type for discriminator ({0}) for slice {1}: {2}
+Unsupported_Identifier_pattern__extensions_are_not_allowed__for_discriminator_for_slice_ = Unsupported Identifier pattern - extensions are not allowed - for discriminator ({0}) for slice {1}
+UNSUPPORTED_IDENTIFIER_PATTERN_NO_PROPERTY_NOT_SUPPORTED_FOR_DISCRIMINATOR_FOR_SLICE = Unsupported: no properties with values found on type {2} for pattern for discriminator ({0}) for slice {1}
+UNSUPPORTED_IDENTIFIER_PATTERN_PROPERTY_NOT_SUPPORTED_FOR_DISCRIMINATOR_FOR_SLICE = Unsupported property {3} on type {2} for pattern for discriminator ({0}) for slice {1}
+UNSUPPORTED_SLICING_COMPLEXITY = Unsupported feature in slicing at {0}: the slicing element at path {1} has slicing {2}, and this nested slicing is not supported
+Unsupported_version_R1 = Unsupported version R1
+Unsupported_version_R2 = Unsupported version R2
+Unsupported_version_R2B = Unsupported version R2B
+Unxpected_internal_condition__no_source_on_diff_element = Unexpected internal condition - no source on diff element
+VALIDATION_AI_FAILED = Consulting AI failed: {0}
+VALIDATION_AI_FAILED_LOG = Consulting AI failed: {0} (see {1} for further details)
+VALIDATION_AI_TEXT_CODE = Apparent mis-match between code ''{0}'' and text ''{1}'': {3} ({2} confidence)
+Validation_BUNDLE_Message = The first entry in a message must be a MessageHeader
+VALIDATION_HL7_PUBLISHER_MISMATCH = The nominated WG ''{0}'' means that the publisher should be ''{1}'' but ''{2}'' was found
+VALIDATION_HL7_PUBLISHER_MISMATCH2 = The nominated WG ''{0}'' means that the publisher should be either ''{1}''or ''{2}'' but ''{3}'' was found
+VALIDATION_HL7_PUBLISHER_MISSING = When HL7 is publishing a resource, the publisher must be provided, and for WG ''{0}'' it should be ''{1}''
+VALIDATION_HL7_PUBLISHER_MULTIPLE_WGS = This resource has more than one workgroup extension (http://hl7.org/fhir/StructureDefinition/structuredefinition-wg)
+VALIDATION_HL7_WG_NEEDED = When HL7 is publishing a resource, the owning committee must be stated using the {0} extension
+VALIDATION_HL7_WG_UNKNOWN = The nominated WG ''{0}'' is unknown
+VALIDATION_HL7_WG_URL = The nominated WG ''{0}'' means that the contact url should be ''{1}'' but it was not found
+VALIDATION_NO_EXPERIMENTAL_CONTENT = Experimental content is not allowed in this context
+Validation_VAL_Content_Unknown = Unrecognized Content {0}
+VALIDATION_VAL_GLOBAL_PROFILE_UNKNOWN = Global Profile reference ''{0}'' from IG {1} could not be resolved, so has not been checked
+VALIDATION_VAL_ILLEGAL_TYPE_CONSTRAINT = Invalid constraint in profile {0} at path {1} - cannot constrain to type {2} from base types {3}
+Validation_VAL_NoType = Unknown type {0}
+VALIDATION_VAL_PROFILE_DEPENDS_NOT_RESOLVED = Profile {1} identifies {0} as a dependency (using the extension http://hl7.org/fhir/StructureDefinition/structuredefinition-dependencies), but this profile could not be found
+Validation_VAL_Profile_MatchMultiple = Profile {0}, Element matches more than one slice - {1}, {2}
+Validation_VAL_Profile_Maximum_one = {3}: max allowed = {7}, but found {0} (from {1})
+Validation_VAL_Profile_Maximum_other = {3}: max allowed = {7}, but found {0} (from {1})
+VALIDATION_VAL_PROFILE_MINIMUM_MAGIC = {0}: magic LOINC code {1} required, but not found (from {2}). Note that other Observation codes are allowed in addition to this required magic code
+Validation_VAL_Profile_Minimum_one = {3}: minimum required = {7}, but only found {0} (from {1})
+Validation_VAL_Profile_Minimum_other = {3}: minimum required = {7}, but only found {0} (from {1})
+Validation_VAL_Profile_Minimum_SLICE_one = Slice ''{3}'': a matching slice is required, but not found (from {1}). Note that other slices are allowed in addition to this required slice
+Validation_VAL_Profile_Minimum_SLICE_other = Slice ''{3}'': minimum required = {0}, but only found {7} (from {1})
+Validation_VAL_Profile_Minimum_SLICE_EXT_one = Slice ''{3}'' for extension ''{8}'': a matching slice is required, but not found (from {1}). Note that other slices are allowed in addition to this required slice
+Validation_VAL_Profile_Minimum_SLICE_EXT_other = Slice ''{3}'' for extension ''{8}'': minimum required = {0}, but only found {7} (from {1})
+Validation_VAL_Profile_MultipleMatches_one = Found multiple matching profiles among {0} choice: {1}
+Validation_VAL_Profile_MultipleMatches_other = Found multiple matching profiles among {0} choices: {1}
+Validation_VAL_Profile_NoCheckMax_one = {3}: Found {0} match, but unable to check max allowed ({2}) due to lack of slicing validation (from {1})
+Validation_VAL_Profile_NoCheckMax_other = {3}: Found {0} matches, but unable to check max allowed ({2}) due to lack of slicing validation (from {1})
+Validation_VAL_Profile_NoCheckMin_one = {3}: Found {0} match, but unable to check minimum required ({2}) due to lack of slicing validation (from {1})
+Validation_VAL_Profile_NoCheckMin_other = {3}: Found {0} matches, but unable to check minimum required ({2}) due to lack of slicing validation (from {1})
+Validation_VAL_Profile_NoDefinition = No definition found for resource type ''{0}''
+Validation_VAL_Profile_NoMatch = Unable to find a match for the specified profile among choices: {0}
+Validation_VAL_Profile_NoSnapshot = StructureDefinition {0} has no snapshot - validation is against the snapshot, so it must be provided
+Validation_VAL_Profile_NotAllowed = This element is not allowed by the profile {0}
+Validation_VAL_Profile_NotSlice = This element does not match any known slice {0} and slicing is CLOSED: {1}
+Validation_VAL_Profile_NoType = The type of element {0} is not known - it could not be determined from the information available. Valid types at this point are {1}
+VALIDATION_VAL_PROFILE_OTHER_VERSION = Profile is for a different version of FHIR ({0}) so has been ignored
+Validation_VAL_Profile_OutOfOrder = As specified by profile {0}, Element ''{1}'' is out of order (found after {2})
+VALIDATION_VAL_PROFILE_SIGNPOST = Validate resource against profile {0}
+VALIDATION_VAL_PROFILE_SIGNPOST_BASE = Validate resource against profile
+VALIDATION_VAL_PROFILE_SIGNPOST_BUNDLE_PARAM = Validate resource against profile {0} - provided as bundle param
+VALIDATION_VAL_PROFILE_SIGNPOST_DEP = Validate resource against profile {0} (per http://hl7.org/fhir/StructureDefinition/structuredefinition-dependencies in {1})
+VALIDATION_VAL_PROFILE_SIGNPOST_GLOBAL = Validate resource against profile {0} - a global profile in {1}
+VALIDATION_VAL_PROFILE_SIGNPOST_META = Validate resource against profile {0} (per meta)
+VALIDATION_VAL_PROFILE_SIGNPOST_OBS = Validate Observation against the {1} profile ({0}) which is required by the FHIR specification because the {2} code {3} was found
+Validation_VAL_Profile_SliceOrder = As specified by profile {0}, Element ''{1}'' is out of order in ordered slice
+VALIDATION_VAL_PROFILE_THIS_VERSION_OK = Profile for this version of FHIR - all OK
+VALIDATION_VAL_PROFILE_THIS_VERSION_OTHER = Profile is for this version of FHIR, but is an invalid type {0}
+Validation_VAL_Profile_Unknown = Profile reference ''{0}'' has not been checked because it could not be found
+VALIDATION_VAL_PROFILE_UNKNOWN_ERROR = Profile reference ''{0}'' has not been checked because it could not be found, and fetching it resulted in the error {1}
+VALIDATION_VAL_PROFILE_UNKNOWN_ERROR_NETWORK = Profile reference ''{0}'' has not been checked because it could not be found, and the host {1} cannot be found
+VALIDATION_VAL_PROFILE_UNKNOWN_NOT_POLICY = Profile reference ''{0}'' has not been checked because it could not be found, and the validator is set to not fetch unknown profiles
+Validation_VAL_Profile_WrongType = Specified profile type was ''{0}'' in profile ''{2}'', but found type ''{1}''
+Validation_VAL_Profile_WrongType2 = Type mismatch processing profile {0} at path {1}: The element type is {4}, but the profile {3} is for a different type {2}
+VALIDATION_VAL_STATUS_INCONSISTENT = The resource status ''{0}'' and the standards status ''{1}'' are not consistent
+VALIDATION_VAL_STATUS_INCONSISTENT_HINT = The resource status ''{0}'' and the standards status ''{1}'' may not be consistent and should be reviewed
+Validation_VAL_Unknown_Profile = Unknown profile {0}
+VALIDATION_VAL_VERSION_NOHASH = Version ''{0}'' contains a ''#'', which is problematic, as this character is used in some URLs to separate the version and the fragment id. Systems will generally wrongly parse these URLs
+VALUESET_BAD_FILTER_EXPR_AND_VALUE = A filter can't have both a value and and expression for the value at the same time
+VALUESET_BAD_FILTER_EXPR_LANG = A ValueSet expression language must be ''text/fhirpath'' not ''{0}''
+VALUESET_BAD_FILTER_EXPR_OR_VALUE = A filter needs a value and or an expression for the value
+VALUESET_BAD_FILTER_EXPR_PARAM_NAME = The filter parameter expression ''{0}'' refers to the unknown parameter ''{1}''
+VALUESET_BAD_FILTER_EXPR_VALUE = The value of the expression ''{0}'' is not a valid FHIRPath: {1}
+VALUESET_BAD_FILTER_OP = The operation ''{0}'' is not allowed for property ''{1}'' in system ''{3}''. Allowed ops: {2}
+VALUESET_BAD_FILTER_VALUE_BOOLEAN = The value for a filter based on property ''{0}'' must be either ''true'' or ''false'', not ''{1}''
+VALUESET_BAD_FILTER_VALUE_CODE = The value for a filter based on property ''{0}'' must be a valid code, not ''{1}''
+VALUESET_BAD_FILTER_VALUE_CODED = The value for a filter based on property ''{0}'' must be in the format system(|version)#code, not ''{1}''
+VALUESET_BAD_FILTER_VALUE_CODED_LEGACY = The value for a filter based on property ''{0}'' should be in the format system(|version)#code, not the coding search pattern ''{1}''
+VALUESET_BAD_FILTER_VALUE_CODED_INVALID = The value for a filter based on property ''{0}'' is ''{1}'' which is not a valid code ({2})
+VALUESET_BAD_FILTER_VALUE_DATETIME = The value for a filter based on property ''{0}'' must be a valid date(/time), not ''{1}''
+VALUESET_BAD_FILTER_VALUE_DECIMAL = The value for a filter based on property ''{0}'' must be a decimal value, not ''{1}''
+VALUESET_BAD_FILTER_VALUE_HAS_COMMA = The filter value has a comma, but the operation is different to ''in'' and ''not-in'', so the comma will be interpreted as part of the {0} value
+VALUESET_BAD_FILTER_VALUE_INTEGER = The value for a filter based on property ''{0}'' must be integer value, not ''{1}''
+VALUESET_BAD_FILTER_VALUE_VALID_CODE = The value for a filter based on property ''{0}'' must be a valid code from the system ''{2}'', and ''{1}'' is not ({3})
+VALUESET_BAD_FILTER_VALUE_VALID_CODE_INACTIVE = The code for the filter ''{0}'' is inactive (''{1}'')
+VALUESET_BAD_FILTER_VALUE_VALID_CODE_CHANGE = The value for a filter based on property ''{0}'' must be a valid code from the system ''{2}'', and ''{1}'' is not ({3}). Note that this is change from the past; terminology servers are expected to still continue to support this filter
+VALUESET_BAD_FILTER_VALUE_VALID_REGEX = The value for a filter based on property ''{0}'' should be a valid regex, not ''{1}'' (err = ''{2}'')
+VALUESET_BAD_PROPERTY_NO_REGEX = Cannot apply a regex filter to the property ''{0}'' (usually regex filters are applied to the codes, or a named property of the code system)
+VALUESET_CIRCULAR_REFERENCE = Found a circularity pointing to {0} processing ValueSet with pathway {1}
+VALUESET_CONCEPT_DISPLAY_PRESENCE_MIXED = This include has some concepts with displays and some without - check that this is what is intended
+VALUESET_CONCEPT_DISPLAY_SCT_TAG_MIXED = This SNOMED-CT based include has some concepts with semantic tags (FSN terms) and some without (preferred terms) - check that this is what is intended (examples for FSN: {0} and examples for no FSN: {1})
+VALUESET_EXAMPLE_SYSTEM_ERROR = Example System ''{0}'' specified, which is illegal. Concepts and Filters can''t be checked
+VALUESET_EXAMPLE_SYSTEM_HINT = Example System ''{0}'' specified, so Concepts and Filters can''t be checked
+VALUESET_IMPORT_UNION_INTERSECTION = This value set has a single include with multiple imported value sets. Per issue https://jira.hl7.org/browse/FHIR-25179, there has been confusion in the past whether these value sets are unioned or intersectioned. If this value set is contained in a package published prior to March 31 2022, it will be treated as a union, otherwise it will be treated as an intersection. If want a union, split the value set imports across multiple includes
+VALUESET_INC_TOO_MANY_CODES = The value set include has too many concepts to validate ({0}), so each individual code has not been checked
+VALUESET_INC_NOT_VALIDATING = The concepts in the value set include have not been validated because the validator is configured not to check them
+VALUESET_INC_NO_SERVER = The concepts in the value set include have not been validated because there is no terminology server
+VALUESET_INC_NO_BATCH_ON_SERVER = The concepts in the value set include have not been validated because the terminology server {0} does not support batch validation (tests version < 1.7.8)
+VALUESET_INC_CS_NO_SUPPORT = The concepts in the value set include have not been validated because the code system is not known, and no terminology service supports it
+VALUESET_INCLUDE_CS_CONTENT = The value set references CodeSystem ''{0}'' which has status ''{1}''
+VALUESET_INCLUDE_CS_MULTI_FOUND = Multiple matching contained code systems found for system ''{0}''
+VALUESET_INCLUDE_CS_NOT_CS = The include system ''{0}'' is a reference to a contained resource, but the contained resource with that id is not a CodeSystem, it''s a {1}
+VALUESET_INCLUDE_CS_NOT_FOUND = No matching contained code system found for system ''{0}''
+VALUESET_INCLUDE_CS_SUPPLEMENT = The value set references CodeSystem ''{0}'' which is a supplement. It must reference the underlying CodeSystem ''{1}'' and use the http://hl7.org/fhir/StructureDefinition/valueset-supplement extension for the supplement
+VALUESET_INCLUDE_CSVER_CONTENT = The value set references CodeSystem ''{0}'' version ''{2}'' which has status ''{1}''
+VALUESET_INCLUDE_CSVER_MULTI_FOUND = Multiple matching contained code systems found for system ''{0}'' version ''{1}''
+VALUESET_INCLUDE_CSVER_NOT_FOUND = No matching contained code system found for system ''{0}'' version ''{1}''
+VALUESET_INCLUDE_CSVER_SUPPLEMENT = The value set references CodeSystem ''{0}'' version ''{2}'' which is a supplement. It must reference the underlying CodeSystem ''{1}'' and use the http://hl7.org/fhir/StructureDefinition/valueset-supplement extension for the supplement
+VALUESET_INCLUDE_INVALID_CONCEPT_CODE = The code ''{1}'' is not valid in the system {0} ({2})
+VALUESET_INCLUDE_INVALID_CONCEPT_CODE_VER = The code ''{2}'' is not valid in the system {0} version {1} ({2})
+VALUESET_INCLUDE_SYSTEM_ABSOLUTE = URI values in ValueSet.compose.include.system must be absolute
+VALUESET_INCLUDE_SYSTEM_ABSOLUTE_FRAG = URI values in ValueSet.compose.include.system must be absolute. To reference a contained code system, use the full CodeSystem URL and reference it using the http://hl7.org/fhir/StructureDefinition/valueset-system extension
+VALUESET_INCLUDE_WRONG_CS_OID = It is not valid to refer to a CodeSystem by an identifier like this ''{0}'' - use ''{1}''
+VALUESET_INCLUDE_WRONG_CS_OID_PLURAL = It is not valid to refer to a CodeSystem by an identifier like this ''{0}'', and the identifier matches to multiple CodeSystem resources ({1})
+VALUESET_INCLUDE_WRONG_VS = The system ''{0}'' is actually a value set
+VALUESET_INCLUDE_WRONG_VS_HINT = The system ''{0}'' is actually a value set, which itself refers to the system ''{1}'' so that may be what is intended here
+VALUESET_INCLUDE_WRONG_VS_MANY = The system ''{0}'' is actually a value set, which itself refers to the systems {1}
+VALUESET_NO_SYSTEM_WARNING = No System specified, so Concepts and Filters can''t be checked
+VALUESET_PARAMETER_MISSING_BINDING_PARAMETER = The ValueSet ''{0}'' has a parameter ''{1}'' but there is no matching binding parameter
+VALUESET_PARAMETER_NAME_WARNING = ValueSet parameter names are recommended to start with ''p-'' but this is ''{0}''
+VALUESET_PARAMETER_NO_DOCO = Without documentation, users likely won't be able to use the valueset parameter ''{0}'' correctly
+VALUESET_PARAMETER_NOT_USED = The value set parameter ''{0}'' is not used
+VALUESET_PARAMETER_UNRECOGNISED_BINDING_PARAMETER =  The binding parameter ''{0}'' is not recognised as a standard parameter or a parameter on the ValueSet ''{1}''
+VALUESET_REFERENCE_INVALID_TYPE_NO_VERSION_0 = Value set System reference ''{0}'' ends with a ''|'' which is suspicious. Note that the reference must not use the canonical version syntax; the version goes in the .version property
+VALUESET_REFERENCE_INVALID_TYPE_NO_VERSION_1 = Value set System references must not use the canonical version syntax - the version ''{0}'' should be in the version property, but that already contains ''{1}''
+VALUESET_REFERENCE_INVALID_TYPE_NO_VERSION_2 = Value set System references must not use the canonical version syntax - the version ''{0}'' should be in the version property, but that already contains ''{1}''
+VALUESET_REFERENCE_INVALID_TYPE_NO_VERSION_3 = Value set System references must not use the canonical version syntax - the version ''{0}'' is already in the version property 
+VALUESET_REFERENCE_INVALID_TYPE = The value set import {0} points to a resource of type {1} which is not valid
+VALUESET_REFERENCE_UNKNOWN = The value set import {0} could not be found so cannot be checked
+VALUESET_SHAREABLE_EXTRA_MISSING = Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.{0} should be present, but it is not 
+VALUESET_SHAREABLE_EXTRA_MISSING_HL7 = Value sets published by HL7 SHALL conform to the ShareableValueSet profile, which says that the element ValueSet.{0} should be present, but it is not
+VALUESET_SHAREABLE_MISSING = Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.{0} is mandatory, but it is not present
+VALUESET_SHAREABLE_MISSING_HL7 = Value sets published by HL7 SHALL conform to the ShareableValueSet profile, which says that the element ValueSet.{0} is mandatory, but it is not present
+VALUESET_SUPPLEMENT_MISSING_one = Required supplement not found: {1}
+VALUESET_SUPPLEMENT_MISSING_other = Required supplements not found: {1}
+VALUESET_TOO_COSTLY = The value set ''{0}'' expansion has too many codes to display ({1})
+VALUESET_TOO_COSTLY_COUNT = The value set ''{0}'' expansion has {2} codes, which is too many to display ({1})
+VALUESET_TOO_COSTLY_TIME = The value set ''{0}'' {2} took too long to process (>{1}sec)
+VALUESET_UNC_SYSTEM_WARNING = Unknown System ''{0}'' specified, so Concepts and Filters can''t be checked (Details: {1})
+VALUESET_UNC_SYSTEM_WARNING_VER = Unknown System/Version ''{0}'' specified, so Concepts and Filters can''t be checked (Details: {1})
+VALUESET_UNKNOWN_FILTER_PROPERTY = The property ''{0}'' is not known for the system ''{1}'', so may not be understood by the terminology ecosystem. Known properties for this system: {2}
+VALUESET_UNKNOWN_FILTER_PROPERTY_NO_CS = No definition can be found for the system {1}, and the property ''{0}'' is not a generally known property, so the property might not be valid, or understood by the terminology ecosystem. In case it''s useful, the list of generally known properties for all systems is {2}
+Version_mismatch_The_context_has_version__loaded_and_the_new_content_being_loaded_is_version_ = Version mismatch. The context has version {0} loaded, and the new content being loaded is version {1}
+VIEWDEFINITION_COLLECTION_NEEDED1 = This column is not defined as a collection, but the path statement ''{0}'' might return multiple values for the column ''{1}'' for some inputs{2}
+VIEWDEFINITION_COLLECTION_NEEDED2 = This column is defined to be not a collection, but the path statement ''{0}'' might return multiple values for the column ''{1}'' for some inputs{2}
+VIEWDEFINITION_COLLECTION_NOT_ALWAYS = The column ''{0}'' is defined as a collection, but collections are not supported in all execution contexts
+VIEWDEFINITION_COLLECTION_NOT_NEEDED = collection is true, but the path statement ''{0}'' can only return single values for the column ''{1}''{2}
+VIEWDEFINITION_COMPLEX_TYPE = Column from path ''{0}'' is a complex type (''{1}''){2}. This is not supported in some Runners
+VIEWDEFINITION_DUPL_COL_NAME = Duplicate Column Name ''{0}''
+VIEWDEFINITION_NAME_INVALID = The {0} name ''{1}'' is not valid
+VIEWDEFINITION_NAME_REQUIRED = A column name is required
+VIEWDEFINITION_NAME_REQUIRED_HINT = A column name is required. The natural name to chose is ''{0}'' (from the path)
+VIEWDEFINITION_PATH_ERROR = Expression Error: {0}{1}
+VIEWDEFINITION_PATH_WARNING = Expression Warning: {0}
+VIEWDEFINITION_PATH_WRONG_RETURN = A where path must return a boolean, but the expression ''{0}'' returns a ''{1}''
+VIEWDEFINITION_SHOULD_HAVE_NAME = No name provided. A name is required in many contexts where a ViewDefinition is used
+VIEWDEFINITION_TYPE_MISMATCH = The path expression ''{0}'' does not return a value of the type ''{1}'' - found ''{2}''{3}
+VIEWDEFINITION_UNABLE_TO_TYPE = Unable to determine a type (found ''{0}''){1}
+VIEWDEFINITION_UNKNOWN_RESOURCE = The name ''{0}'' is not a valid resource{1}
+VS_EXP_FILTER_UNK = ValueSet ''{0}'' Filter by property ''{1}'' and op ''{2}'' is not supported yet
+VS_EXP_IMPORT_CS = Cannot include value set ''{0}'' because it''s actually a code system
+VS_EXP_IMPORT_CS_PINNED =  Cannot include value set ''{0}'' version ''{1}'' because it''s actually a code system
+VS_EXP_IMPORT_CS_PINNED_X =  Cannot exclude value set ''{0}'' version ''{1}'' because it''s actually a code system
+VS_EXP_IMPORT_CS_X = Cannot exclude value set ''{0}'' because it''s actually a code system
+VS_EXP_IMPORT_ERROR = Unable to expand included value set ''{0}'': {1}
+VS_EXP_IMPORT_ERROR_X = Unable to expand included value set ''{0}'', but no error
+VS_EXP_IMPORT_FAIL = Unable to expand included value set {0}
+VS_EXP_IMPORT_FAIL_X = Unable to expand excluded value set {0}
+VS_EXP_IMPORT_NULL = Unable to find included value set with no identity
+VS_EXP_IMPORT_NULL_X = Unable to find excluded value set with no identity
+VS_EXP_IMPORT_UNK = Unable to find included value set ''{0}''
+VS_EXP_IMPORT_UNK_PINNED = Unable to find included value set ''{0}'' version ''{1}''
+VS_EXP_IMPORT_UNK_PINNED_X = Unable to find excluded value set ''{0}'' version ''{1}''
+VS_EXP_IMPORT_UNK_X = Unable to find excluded value set ''{0}''
+Wrong_namespace__expected_ = Wrong namespace - expected ''{0}''
+Wrong_type_for_resource = Wrong type for resource
+TEXT_LINK_DATA_NOT_FOUND = The target of the textLink data reference ''{0}'' was not found in the resource
+TEXT_LINK_DATA_MULTIPLE_MATCHES = Multiple matching targets for the textLink data reference ''{0}'' were found in the resource
+XHTML_URL_DATA_DATA_INVALID = The data should be valid base64 content for a data: URL: {0}
+XHTML_URL_DATA_DATA_INVALID_COMMA = Comma found in data portion of data URL: {0}
+XHTML_URL_DATA_MIMETYPE = The mimetype portion of the data: URL is not valid ({1}) in URL: {0}
+XHTML_URL_DATA_NO_DATA = No data found in data: URL
+XHTML_URL_EMPTY = URL is empty
+XHTML_URL_INVALID = The URL is not valid because ''({1})'': {0}
+XHTML_URL_INVALID_CHARS_one = URL contains Invalid Character: {1}
+XHTML_URL_INVALID_CHARS_other = URL contains {0} Invalid Characters: {1}
+XHTML_XHTML_Attribute_Illegal = Invalid attribute name in the XHTML (''{0}'' on ''{1}'')
+XHTML_XHTML_ATTRIBUTE_XML_SPACE = The attribute ''xml:space'' is legal but has a fixed value of ''preserve''. Its use is discouraged
+XHTML_XHTML_DOCTYPE_ILLEGAL = Malformed XHTML: Found a DocType declaration, and these are not allowed (XXE security vulnerability protection)
+XHTML_XHTML_Element_Illegal = Invalid element name in the XHTML (''{0}'')
+XHTML_XHTML_ELEMENT_ILLEGAL_IN_PARA = Invalid element name inside a paragraph in the XHTML (''{0}'')
+XHTML_XHTML_Entity_Illegal = Invalid entity in the XHTML (''{0}'')
+XHTML_XHTML_Image_Reference_Illegal = Invalid Image Reference in the XHTML (''{0}'')
+XHTML_XHTML_Name_Invalid = Wrong name on the XHTML (''{0}'') - must start with div
+XHTML_XHTML_NS_InValid = Wrong namespace on the XHTML (''{0}'', should be ''{1}'')
+xml_attr_value_invalid = The XML Attribute {0} has an invalid character
+xml_encoding_invalid = The XML encoding is invalid (must be UTF-8, not ''{0}'')
+XSI_TYPE_UNNECESSARY = xsi:type is unnecessary at this point
+XSI_TYPE_WRONG = The xsi:type value ''{0}'' is wrong (should be ''{1}''). Note that xsi:type is unnecessary at this point
+VALIDATION_VAL_NAMED_EXTENSIONS_NOT_FOUND = The context indicates that this element contains named extensions, but no named extensions holder element was found in {0}
+VALIDATION_VAL_NAMED_EXTENSIONS_BAD_TYPE = The type {3} cannot be used in the location {0}#{1}: must be a type of {2} 
+VALIDATION_VAL_NAMED_EXTENSIONS_BAD_CONTEXT = The extension definition {0} defines the contexts of use as {2}, which does not match the location of use which is {3}
+VALIDATION_VAL_NAMED_EXTENSIONS_NO_CONTEXT = The extension definition {0} does not define any contexts of use, so the context cannot be validated
+SD_ADDITIONAL_BASE_INCOMPATIBLE_VALUES = Unable to apply additional base {0} at path {1}: incompatible values {2} and {3}
+DN_SLICE_NO_DEFINITION = Found a slice at ''{0}'' but there was no definition for the slicing
+SD_ADDITIONAL_BASE_INDETERMINATE_TYPE = Unable to determine the type of the element at {0}#{1}
+SD_ADDITIONAL_BASE_NO_TYPE = Unable to find a type profile that conforms to both {2} and {3} at {0}#{1}
+QUESTIONNAIRE_QR_ITEM_NOT_ATTACHMENT_MIMETYPE = A mime type is required for this answer
+QUESTIONNAIRE_QR_ITEM_BAD_ATTACHMENT_MIMETYPE = The mime type {0} is not valid for this answer (allowed = {1})
+QUESTIONNAIRE_QR_ITEM_BAD_ATTACHMENT_LENGTH = The attachment is too large (allowed = {0}, found = {1})
+QUESTIONNAIRE_QR_ITEM_EXCLUSIVE = Selected answer {0} is an exclusive option - can''t select anything else at the same time
+QUESTIONNAIRE_QR_ITEM_DATE_MIN =  The value {0} is less than the allowed minimum of {1}
+QUESTIONNAIRE_QR_ITEM_DATE_MAX = The value {0} is greater than the allowed maximum of {1}
+QUESTIONNAIRE_QR_ITEM_DATE_VALUE_EXCEPTION = An error occurred checking the date: {0}
+QUESTIONNAIRE_QR_ITEM_TIME_MIN =  The value {0} is less than the allowed minimum of {1}
+QUESTIONNAIRE_QR_ITEM_TIME_MAX = The value {0} is greater than the allowed maximum of {1}
+QUESTIONNAIRE_QR_ITEM_TIME_VALUE_EXCEPTION = An error occurred checking the time: {0}
+QUESTIONNAIRE_QR_ITEM_DECIMAL_MIN =  The value {0} is less than the allowed minimum of {1}
+QUESTIONNAIRE_QR_ITEM_DECIMAL_MAX = The value {0} is greater than the allowed maximum of {1}
+QUESTIONNAIRE_QR_ITEM_DECIMAL_VALUE_EXCEPTION = An error occurred checking the value: {0}
+QUESTIONNAIRE_QR_ITEM_NOOPTIONSDECIMAL = Cannot validate decimal answer option because no option list is provided
+QUESTIONNAIRE_QR_ITEM_NODECIMAL = The value {0} is not in the set of permitted values
+QUESTIONNAIRE_QR_ITEM_DECIMAL_MAX_DECIMALS = The value {0} has too many decimal places (limit = {1})
+QUESTIONNAIRE_QR_ITEM_DISPLAY_NO_VALUE = Items of type ''display'' cannot have answers
+QUESTIONNAIRE_QR_ITEM_INTEGER_MIN = The value {0} is less than the allowed minimum of {1}
+QUESTIONNAIRE_QR_ITEM_INTEGER_MAX = The value {0} is greater than the allowed maximum of {1}
+QUESTIONNAIRE_QR_ITEM_INTEGER_VALUE_EXCEPTION = An error occurred checking the value: {0}
+QUESTIONNAIRE_QR_ITEM_QUANTITY_MIN = The quantity {0} is less than the allowed minimum of {1}
+QUESTIONNAIRE_QR_ITEM_QUANTITY_MAX = The quantity {0} is greater than the allowed maximum of {1}
+QUESTIONNAIRE_QR_ITEM_DECIMAL_CANNOT_COMPARE_MIN = The quantity {0} cannot be compared to the allowed minimum of {1}
+QUESTIONNAIRE_QR_ITEM_DECIMAL_CANNOT_COMPARE_MAX = The quantity {0} cannot be compared to the allowed maximum of {1}
+QUESTIONNAIRE_QR_ITEM_DECIMAL_CANNOT_COMPARE_MIN_UNITS = The quantity {0} cannot be compared to the allowed minimum of {1} because no formal units are specified
+QUESTIONNAIRE_QR_ITEM_DECIMAL_CANNOT_COMPARE_MAX_UNITS = The quantity {0} cannot be compared to the allowed maximum of {1} because no formal units are specified
+QUESTIONNAIRE_QR_ITEM_DECIMAL_INVALID_UNITS = The value {0} has a unit that is not valid (allowed = {1})
+QUESTIONNAIRE_QR_ITEM_DECIMAL_INVALID_UNIT_VS = The unit value set ''{1}'' could not be found
+QUESTIONNAIRE_QR_ITEM_DECIMAL_UNIT_FAIL_VS = The value {0} has a unit that is not in the unit value set ''{1}''
+QUESTIONNAIRE_QR_ITEM_MAX_OCCURS = The maximum number of answers is {0} but this has {1} answers
+QUESTIONNAIRE_QR_ITEM_MIN_OCCURS = The minimum number of answers is {0} but this has {1} answers
+QUESTIONNAIRE_QR_ITEM_STRING_MIN_LENGTH = The answer ''{0}'' is shorter then the required minimum length of {1}
+QUESTIONNAIRE_QR_ITEM_STRING_MAX_LENGTH = The answer ''{0}'' is longer then the allowed maximum length of {1}
+QUESTIONNAIRE_QR_ITEM_STRING_REGEX = The answer ''{0}'' does not conform to the required regex ''{1}''
+QUESTIONNAIRE_QR_ITEM_STRING_REGEX_EF = The answer ''{0}'' does not conform to the expected format ''{2}'' (regex ''{1}'')
+QUESTIONNAIRE_QR_ITEM_STRING_ILLEGAL_CHARS = The answer should not contain new line characters
+QUESTIONNAIRE_QR_ITEM_GROUP_REQUIRED = No sub-items found for required group
+QUESTIONNAIRE_QR_ITEM_VS_BAD = The value set ''{1}'' could not be found
+QUESTIONNAIRE_QR_ITEM_VS_FAIL = The value ''{0}'' is not in the list of allowed values (value set ''{1}'')
+REFERENCE_REF_INVALID_REF = The reference ''{0}'' is not a valid reference
+QUESTIONNAIRE_QR_ITEM_REF_INVALID = The resource type ''{0}'' in the reference {1} is not allowed (allowed = {2})
+QUESTIONNAIRE_QR_ITEM_REF_CANT = Unable to determine the resource type, so the resource type can''t be checked
+QUESTIONNAIRE_QR_ITEM_REF_INVALID_GENERAL = The resource type {0} in the reference {1} is not valid
+QUESTIONNAIRE_QR_AUTHOR_START = The authored date ''{0}'' is before the start of the permitted period defined in the Questionnaire (''{1}'')
+QUESTIONNAIRE_QR_AUTHOR_END = The authored date ''{0}'' is after the end of the permitted period defined in the Questionnaire (''{1}'')
+CONCEPTMAP_GROUP_TARGET_DUPLICATION_DIFFERENT = A {2} relationship has already been defined from the code {0} to the code {1}, but this defines a new relationship {3}
+CONCEPTMAP_GROUP_TARGET_DUPLICATION = A {2} relationship has already been defined from the code {0} to the code {1}
+TEXT_LINK_NO_DIV = A textLink extension was found, but there was no xhtml element present for that targets of the html references
+TEXT_LINK_NO_ID = The html id ''{0}'' was not found in the xhtml
+TEXT_LINK_NO_DATA = No data element was found in the textLink extension
+TEXT_LINK_SELECTOR_INVALID = The textLink selector ''{0}'' is invalid: {1}
+SD_CONTEXT_SHOULD_ELEMENT_NOT_FOUND = The element {0} is not valid
+SD_CONTEXT_SHOULD_ELEMENT_NOT_FOUND_VER = The element {0} is not valid in version {1}
+FILTER_NOT_UNDERSTOOD = The filter "{0} {1} {2}" from the value set {3} was not understood in the context of {4}
+XHTML_CONTROL_NO_SOURCE = The xhtml node at ''{0}'' does not have a class attribute to indicate its source (boilerplate, generated, or original) and this is required by the profile {1}
+XHTML_XHTML_MIXED_LANG = The xhtml has some language sections ({0}), and also has content that is not in a language section
+XHTML_CONTROL_NO_LANGS = The xhtml has some language sections ({0}), but language sections are prohibited in this context by the profile {1}
+XHTML_CONTROL_LANGS_REQUIRED = The xhtml has no language sections, but language sections are required in this context by the profile {1}
+XHTML_CONTROL_LANGS_NONE_NO_DEFAULT = The profile {1} requires a section in the narrative for the resource language, but there is no sections and no resource language
+XHTML_CONTROL_LANGS_NONE = The profile {1} requires a section in the narrative for the resource language {0}, but there is no sections
+XHTML_CONTROL_LANGS_NO_DEFAULT = The profile {1} requires a section in the narrative for the resource language, but there is no language
+XHTML_CONTROL_LANGS_REQUIRED_DEF = The profile {2} requires a section in the narrative for the resource language ({0}), but it was not found (found {1})
+XHTML_CONTROL_LANGS_NONE2 = The profile {1} requires a section in the narrative for the language {0}, but there is no sections
+XHTML_CONTROL_LANGS_REQUIRED_LANG = The profile {2} requires a section in the narrative for the language ''{0}'', but it was not found (found {1})
+XHTML_XHTML_DUPLICATE_IDS = The XHTML  the resource contains more than one node for each of the following node ids and anchor names: {0}
+BUNDLE_SIGNATURE_NOT_CHECKED_KIND = The signature format ''{0}'' is not checked (known formats: application/jose and application/pkcs7-signature)
+BUNDLE_SIGNATURE_NOT_CHECKED_DATA = There is no actual signature data, so the {0} signature cannot be checked
+BUNDLE_SIGNATURE_HEADER_PARSE = Error parsing the digital signature header: {0}
+BUNDLE_SIGNATURE_HEADER_WHEN_MISMATCH = The time in the signature {0} is not the same as the stated time {1}
+BUNDLE_SIGNATURE_PAYLOAD_PRESENT = The signature has a payload, but the signature should be a detached signature with no payload
+BUNDLE_SIGNATURE_PAYLOAD_INVALID = The payload provided could not be read - invalid Base64 content ({0})
+BUNDLE_SIGNATURE_PAYLOAD_INVALID_JSON = The payload provided could not be read - invalid JSON Structure ({0})
+BUNDLE_SIGNATURE_PAYLOAD_MISMATCH = The signature cannot be valid because the content to sign ({0} bytes} is not the same as the signed content ({1} bytes)
+BUNDLE_SIGNATURE_PAYLOAD_CANON_DEFAULT = No canonicalization found, so using {0}
+BUNDLE_SIGNATURE_PAYLOAD_JSON_MATCHES = The actual JSON structures of payload and canonicalized form do match, so the issue is in the canonicalization
+BUNDLE_SIGNATURE_PAYLOAD_JSON_NO_MATCH = The actual JSON structures of payload and canonicalized form do not match: {0}
+BUNDLE_SIGNATURE_SIG_INVALID = The actual signature is not valid base64: {0}
+BUNDLE_SIGNATURE_SIG_FAIL_KID = The signature did not verify against the certificate using the key with id {0}
+BUNDLE_SIGNATURE_SIG_FAIL_CERT = The signature did not verify against the provided certificate
+BUNDLE_SIGNATURE_SIG_FAIL_CERT_ID = The signature did not verify against the provided certificate (key id = {0})
+BUNDLE_SIGNATURE_SIG_ERROR = Error verifying the signature against the certificate: {0}
+BUNDLE_SIGNATURE_CHECKED_DATA_B64 = The signature data is not valid base64 content, but it looks like native application/jose, so it will be checked anyway
+BUNDLE_SIGNATURE_NOT_CHECKED_DATA_B64 = The signature data is not valid base64 content, so the signature cannot be checked
+BUNDLE_SIGNATURE_PAYLOAD_BASE64_DIFF = The signed bytes are identical, but the base64 representations differ
+BUNDLE_SIGNATURE_SIG_OK = The signature verified OK
+BUNDLE_SIGNATURE_NO_SIG_FORMAT = There is no value for sigFormat. In the absence of a stated signature format, the signature cannot be interpreted reliably (or validated)
+BUNDLE_SIGNATURE_SIG_FORMAT_JOSE = Signature looks like application/jose, so validating accordingly
+BUNDLE_SIGNATURE_HEADER_X509_ERROR = Unable to parse X509 Certificate: {0}
+BUNDLE_SIGNATURE_HEADER_NO_SIG_TIME = The signature does not have a signing time (sigT in the header)
+BUNDLE_SIGNATURE_CANON_DIFF = The canonicalization in the digital signature is {0} which doesn't match the value {1} found in the targetFormat
+BUNDLE_SIGNATURE_HEADER_NO_KID_OR_CERT = Didn''t find a provided certificate or a ''kid'' in the header, so can''t verify the signature
+BUNDLE_SIGNATURE_HEADER_CERT_NOT_FOUND = Didn''t find a matching certificate for the ''kid'' {0} in the header, so can''t verify the signature
+BUNDLE_SIGNATURE_SIGNED_BY = The content claims to have been signed by {0}, but this has not been verified
+BUNDLE_SIGNATURE_SIGNED_BY_VERIFIED = The content was signed by {0} (and this has been verified by the signature)
+BUNDLE_SIGNATURE_SIGNED_AT_VERIFIED = The content was signed at {0} (and this has been verified by the signature)
+BUNDLE_SIGNATURE_SIGNED_AT = The content claims to have been signed at {0}, but this has not been verified
+BUNDLE_SIGNATURE_SIGNED_FOR_VERIFIED = The content was signed for the purpose of {1} ({0}) (and this has been verified by the signature)
+BUNDLE_SIGNATURE_SIGNED_FOR = The content claims that it was signed for the purpose of {1} ({0}), but this has not been verified
+BUNDLE_SIGNATURE_HEADER_SIG_TIME_WRONG_FORMAT = The sigT header has the wrong format: {0}
+BUNDLE_SIGNATURE_HEADER_CERT_NOT_FOUND_ERROR = Error scanning for certificate to match kid {0}: {1}
+BUNDLE_SIGNATURE_WHO_MISMATCH = The  Signature.who.identifier ''{0}'' does not match a subject value from the certificate (one of {1})
+BUNDLE_SIGNATURE_WHO_RECOMMENDED = A certificate subject identifier should also be found in Signature.who.identifier (one of {0})
+BUNDLE_SIGNATURE_WHO_NO_INFO = Neither the digital signature nor Signature.who are provided to identify the signer
+BUNDLE_SIGNATURE_WHO_NOT_IN_CERT = The Signature.who value is not found in the digital signature
+BUNDLE_SIGNATURE_CANON_ERROR = Error parsing the targetFormat ''{0}'': {1}
+BUNDLE_SIGNATURE_DIGSIG_INVALID = The digital signature is invalid XML: {0}
+BUNDLE_SIGNATURE_DIGSIG_NO_SIG_TIME = No SigningTime element found in the digital signature
+BUNDLE_SIGNATURE_DIGSIG_WHEN_MISMATCH = The time in the digital signature {0} is not the same as the stated time {1}
+BUNDLE_SIGNATURE_DIGSIG_X509_ERROR = Unable to parse X509 Certificate: {0}
+BUNDLE_SIGNATURE_DIGSIG_NO_CERT = Didn''t find a provided X509 certificate in the digital signature, so can''t verify the signature
+BUNDLE_SIGNATURE_DIGSIG_NO_SV = Didn''t find a provided signedValue in the digital signature, so can''t verify the signature
+BUNDLE_SIGNATURE_DIGSIG_SIG_ERROR = Error verifying the signature: {0}
+BUNDLE_SIGNATURE_DIGSIG_NO_REFERENCES = No references found in the digital signature SignedInfo
+BUNDLE_SIGNATURE_DIGSIG_REFERENCES_TOO_MANY = Too many references found in the digital signature SignedInfo - not understood
+BUNDLE_SIGNATURE_DIGSIG_REFERENCE_NOT_UNDERSTOOD = The reference in the SignedInfo in the digital signature is ''{0}'' which is not understood (or correct?)
+BUNDLE_SIGNATURE_DIGSIG_REFERENCE_TYPE_NOT_UNDERSTOOD = The second reference in the SignedInfo in the digital signature has type ''{0}'' which is not understood (or correct?)
+BUNDLE_SIGNATURE_SIG_DIGEST_MISMATCH = The digest value for the signed content doesn''t match the provided content ({0} vs {1}). The signature is not valid
+BUNDLE_SIGNATURE_DIGSIG_SIGNED_SAME = The signed bytes are identical, so the signature failure is not because the content changed. Check Canonicalization carefully (including whitespace)
+BUNDLE_SIGNATURE_SIG_DIGEST_MISMATCH_XADES = The digest value for the XaDeS signed content doesn''t match the provided content ({0} vs {1}). The signature is not valid. Check XML canonicalization carefully, particularly with regard to whitespace and namespaces
+BUNDLE_SIGNATURE_DIGSIG_SIGNED_INVALID = The digital signature is not valid XML: {0}
+BUNDLE_SIGNATURE_DIGSIG_SIGNED_MISMATCH = The signature cannot be valid because the content to sign ({0} bytes} is not the same as the signed content ({1} bytes)
+BUNDLE_SIGNATURE_DIGSIG_SIGNED_INVALID_XML =  The signed bytes provided could not be read - invalid XML Structure ({0})
+BUNDLE_SIGNATURE_DIGSIG_SIGNED_XML_MATCHES = The actual XML structures of payload and canonicalized form do match, so the issue is in the canonicalization
+BUNDLE_SIGNATURE_DIGSIG_SIGNED_XML_NO_MATCH = The actual XML structures of payload and canonicalized form do not match: {0}
+VALUESET_BAD_FILTER_VALUE_INVALID = The value ''{1}'' for the filter {0} is invalid: {2}
+VALUESET_BAD_FILTER_VALUE_CANT_CHECK = The value ''{1}'' for the filter {0} can''t be checked: {2}
+XHTML_XHTML_BLOCK_IN_PARA = Found block structures inside a paragraph/text element {0} at {1}: {2}
+XHTML_XHTML_NO_RECURSION = Elements of type {0} at {1} cannot contain nested {0} at {2}
+XHTML_XHTML_NO_CHILDREN = Elements of type {0} cannot have children
+XHTML_XHTML_OUT_OF_PLACE = Elements of type {0} must be in a {1}, not a {2} at {3}
+XHTML_XHTML_ILLEGAL_CHILDREN = Elements of type {0} at {1} cannot have the following children: {2}
+XHTML_XHTML_BAD_ELEMENT_TYPE = Elements of type [{0}] cannot appear at {1}
+TYPE_SPECIFIC_CHECKS_DT_ATT_B64_DECODE_FAIL = The base64 content in the {0} element is not valid base64: {1}
+TYPE_SPECIFIC_CHECKS_DT_ATT_HASH_MISMATCH = The hash of the data did not match the data (stated: ''{0}'', actual: ''{1}'')
+BUNDLE_SIGNATURE_CERT_DETAILS = Signing Certificate Details: Subject=''{0}'', Issuer=''{1}'', Serial=''{2}''
+BUNDLE_SIGNATURE_CERT_SOURCE = Signing Certificate Source: {0}
+VALUESET_TXVER_BATCH_NOT_SUPPORTED = The terminology server {2} used for the CodeSystem {1} does not support batch validation (tx version {0}), so the codes have not been validated
+SD_ED_BIND_ALL_LOINC_CODES = This binding is to ALL LOINC codes, which includes part codes and answer list codes. The value set choice should be reviewed
+SD_ED_BIND_ALLSCT_CODES = This binding is to ALL SNOMED CT codes, which includes qualifiers etc. The value set choice should be reviewed
+SD_ED_BIND_ALL_CPT_CODES = This binding is to ALL CPT codes, which includes modifiers and internal metadata codes. The value set choice should be reviewed
+RESOURCE_INTERNAL_USE_ONLY = This {0} comes from the package {1} which has been marked as not suitable for this use
+TYPE_SPECIFIC_CHECKS_DT_SID_INCORRECT = The URL {0} is not a correct URL to use (in spite of being in the standard, and/or accepted in the past)
+INACTIVE_DISPLAY_FOUND_one =  ''{1}'' is no longer considered a correct display for code ''{2}'' (status = {4}). The correct display is ''{3}''
+INACTIVE_DISPLAY_FOUND_other = ''{1}'' is no longer considered a correct display for code ''{2}'' (status = {4}). The correct display is one of {3}
+INACTIVE_CONCEPT_FOUND =  The concept ''{1}'' has a status of {0} and its use should be reviewed
+DEPRECATED_CONCEPT_FOUND = The concept ''{1}'' is deprecated and its use should be reviewed
+CONCEPT_DEPRECATED_IN_VALUESET = The presence of the concept ''{1}'' in the system ''{0}'' in the value set {3} is marked with a status of {2} and its use should be reviewed
+SYSTEM_VERSION_MULTIPLE_OVERRIDE = Multiple version overrides found for system {0}: ''{1}'', ''{2}'');
+SYSTEM_VERSION_MULTIPLE_DEFAULT = Multiple default versions found for system {0}: ''{1}'', ''{2}'');
+VALUESET_VERSION_CHECK = The version ''{1}'' is not allowed for system ''{0}'': required to be ''{2}'' by a version-check parameter
+VALUESET_VALUE_MISMATCH = The code system ''{0}'' version ''{1}'' in the ValueSet include is different to the one in the value (''{2}'')
+VALUESET_VALUE_MISMATCH_CHANGED = The code system ''{0}'' version ''{1}'' resulting from the version ''{2}'' in the ValueSet include is different to the one in the value (''{3}'')
+VALUESET_VALUE_MISMATCH_DEFAULT = The code system ''{0}'' version ''{1}'' for the versionless include in the ValueSet include is different to the one in the value (''{3}'')
+TERMINOLOGY_TX_NO_OID_SERVICES = OIDs cannot be verified because the context of use does not provide OID services
+VALIDATION_ADDITIONAL_RESOURCE_NO = This resource is not an additional resource, so should not have a resourceDefinition of ''{0}''
+VALIDATION_ADDITIONAL_RESOURCE_NO_WRONG = The value for resourceDefinition of ''{0}'' does not match the required value of ''{1}''. In addition, this is not an additional resource, and shouldn''t have a resourceDefinition at all
+VALIDATION_ADDITIONAL_RESOURCE_ABSENT = This resource is an additional resource, so must have a resourceDefinition of ''{0}''
+VALIDATION_ADDITIONAL_RESOURCE_WRONG = The value for resourceDefinition of ''{0}'' must be ''{1}''
+RESOURCEDEFINITION_PROPERTY_WRONG_TYPE = The JSON element for ''resourceDefinition'' has the wrong JSON type: {0}
+RESOURCEDEFINITION_PROPERTY_UNKNOWN = The ''resourceDefinition'' is ''{0}'', but no additional resource is known for that reference
+CONFORMANCE_STATEMENT_WORD = The html source contains the word ''{0}'' but it is not in a text phrase marked as a conformance clause
+VALUESET_CODE_CONCEPT_HINT = {3}. 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
+VALUESET_CODE_CONCEPT_HINT_VER ={3}. 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
+TERMINOLOGY_TX_SYSTEM_UNSUPPORTED = The code cannot be checked because codeSystem ''{0}'' version ''{1}'' is not supported ({2})