Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-40259

subdepartment extension, not where it belongs

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci PAS (FHIR)
    • 1.2.0-ballot [deprecated]
    • Financial Mgmt
    • IdentifierJurisdiction
      IdentifierSubDepartment
    • Hide

      We will adjust the description of the subdepartment extension to be:

      "An additional element that provides a further subdivision within the organization granting the identifier"

      Jurisdiction was added in a previous issue because the implementing systems did not want to have to map between the various driver's license OIDs to the underlying jurisdiction.  It is a denormalization but was identified in that issue as being a reasonable optimization.

      We will adjust the description to be:
      "An additional element that provides the assigning jurisdiction of the identifier (i.e. provider state license number or state driver's license) so that it does not need to be mapped from the identifier system."

      Show
      We will adjust the description of the subdepartment extension to be: "An additional element that provides a further subdivision within the organization granting the identifier " Jurisdiction was added in a previous issue because the implementing systems did not want to have to map between the various driver's license OIDs to the underlying jurisdiction.  It is a denormalization but was identified in that issue as being a reasonable optimization. We will adjust the description to be: "An additional element that provides the assigning jurisdiction of the identifier (i.e. provider state license number or state driver's license) so that it does not need to be mapped from the identifier system."
    • Bob Dieterle / Jeff Brown : 8-0-0
    • Clarification
    • Non-substantive

    Description

      The subdepartment extension has this description. "An additional element that provides the subdepartment that created the authorization request."

      However it's described on an identifier, which has broader utilization that just an authorization request. As this extension extends "authorization request" then it belongs on the resource that is an authorization request. (Claim?)

       

      Jurisdiction extension is weird. The description is, put data here so you don't have to lookup data where it belongs. (This is called de-normalization, "Put the patient data on the condition resource so we don't have to fetch the patient resource." Typically the wrong thing to do.)

      The example is "state dl". My DL issued by NC is good in all 50 states, even though NC has no "jurisdiction" in SC. Is it jurisdiction of the issuing authority or jurisdiction of "where valid at". Also shouldn't the jurisdiction be on "the thing" (like a qualification, or a license) not an identifier on "the thing". As technically, every issued identifier, has global identifier jurisdiction, even if the thing it identifies does not.

      Attachments

        Activity

          People

            Unassigned Unassigned
            dventon Daniel Venton
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: