Jan 2015 Ballot Comment #149

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Administration
    • HealthcareService
    • 5.6.1
    • Hide

      Agree that there is insufficient usage guidance/use cases?and examples for this resource, these will be added.

      The category on the resources page will remain under attribution, as this is not specifically just for appointments/scheduling.

      PA will seek more input from other implementers.

      ?

      Show
      Agree that there is insufficient usage guidance/use cases?and examples for this resource, these will be added. The category on the resources page will remain under attribution, as this is not specifically just for appointments/scheduling. PA will seek more input from other implementers. ?
    • Clarification
    • Non-substantive
    • DSTU1 [deprecated]

      Comments
      Healthcare Service is very unclear because it is so generic and there is very little description. What is it for? What level of granularity? There need to be some good examples. I presume it is not supposed to be for detailed clinical acts (e.g., tests/observations or procedures) that can be performed there, e.g., Urinalysis or Appendectomy. Is it supposed to be for high level categories of services that an organization might advertise to the public, such as "Obstetrics" or "Neonatal Care?" Some examples would really be helpful, but there are no meaningful examples in the Examples tab. Until it is clarified, this Resource should not even be in FHIR, as implementers would not know when/how to use it. IF this is a service for which an appointment can be scheduled, shouldn't it be in the "Scheduling/Ordering" category?

      Grahame's Comments
      no opinion

            Assignee:
            Unassigned
            Reporter:
            david_tao
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: