Publish Box goes here

• Narrative Content
• XML
• JSON
• TTL

: AS.1 Manage Provider Information (Header) - JSON Representation

Active as of 2024-11-26

Raw json | Download

{
  "resourceType" : "Requirements",
  "id" : "EHRSFMR2.1-AS.1",
  "meta" : {
    "profile" : [
      🔗 "http://hl7.org/ehrs/StructureDefinition/FMHeader"
    ]
  },
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n    <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Maintain, or provide access to, current provider information.</p>\n</div></span>\n\n    \n    <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Manage the information regarding providers within and external to an organization that is required to support care provision. This information includes a registry of providers (internal to the EHR-S or external), the provider's location, on-call information, and office information. Information regarding teams or groups of providers as well as individual patient relationships with providers is necessary to support care coordination and access to patient information.\nExample:\nFor example, a hospital's directory ought to contain the full name, specialty, credentials, address, and contact information for each provider. A directory might also manage information regarding a given provider's work assignment/allocation, expectations, and/or history (e.g., the percentage of time planned towards (or devoted to) patient care, research, teaching, administration, and/or other duties). Directory Information could also describe the type of care offered by a given care provider (e.g, cardiologist or general practitioner), health care setting (e.g., long term care facility or hospital), and categories of patient (e.g., children or geriatric patients).</p>\n</div></span>\n    \n\n    \n\n    \n    <table id=\"statements\" class=\"grid dict\">\n        \n    </table>\n</div>"
  },
  "url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.1",
  "version" : "2.1.0",
  "name" : "AS_1_Manage_Provider_Information",
  "title" : "AS.1 Manage Provider Information (Header)",
  "status" : "active",
  "date" : "2024-11-26T16:30:50+00:00",
  "publisher" : "EHR WG",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/ehr"
        }
      ]
    }
  ],
  "description" : "Maintain, or provide access to, current provider information.",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code" : "001",
          "display" : "World"
        }
      ]
    }
  ],
  "purpose" : "Manage the information regarding providers within and external to an organization that is required to support care provision. This information includes a registry of providers (internal to the EHR-S or external), the provider's location, on-call information, and office information. Information regarding teams or groups of providers as well as individual patient relationships with providers is necessary to support care coordination and access to patient information.\nExample:\nFor example, a hospital's directory ought to contain the full name, specialty, credentials, address, and contact information for each provider. A directory might also manage information regarding a given provider's work assignment/allocation, expectations, and/or history (e.g., the percentage of time planned towards (or devoted to) patient care, research, teaching, administration, and/or other duties). Directory Information could also describe the type of care offered by a given care provider (e.g, cardiologist or general practitioner), health care setting (e.g., long term care facility or hospital), and categories of patient (e.g., children or geriatric patients)."
}