Difference between revisions of "Endpoint FHIR Resource Proposal"
(Created page with "{{subst::Template:FHIR Resource Proposal}}") |
|||
| Line 13: | Line 13: | ||
| − | = | + | =Endpoint= |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Owning committee name== | ==Owning committee name== | ||
| + | Patient Administration | ||
| − | |||
| − | |||
==Committee Approval Date:== | ==Committee Approval Date:== | ||
<i>Please enter the date that the committee approved this Resource proposal</i> | <i>Please enter the date that the committee approved this Resource proposal</i> | ||
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
| − | + | FHIR-Infrastructure | |
| − | |||
| − | |||
| − | |||
| − | |||
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
| − | + | pending | |
| − | |||
==Scope of coverage== | ==Scope of coverage== | ||
| + | An endpoint describes the technical details of a location that can be connected to for the delivery/retrieval of information. Sufficient information is required to ensure that a connection can be made securely, and appropriate data transmitted as defined by the endpoint owner. This is not a description of details of the current system, as found in conformance, but of another (potentially external) system. | ||
| + | These may be locally hosted services, regional services, or national service. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==RIM scope== | ==RIM scope== | ||
| − | + | ? | |
<!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | <!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | ||
==Resource appropriateness== | ==Resource appropriateness== | ||
| − | + | All systems that integrate with other systems have a need to track the details of the connectivity. | |
| − | + | This resource permits recording of this information, and will be able to be included in Registries where they can be discovered, or internally to manage external dependencies. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Expected implementations== | ==Expected implementations== | ||
| Line 82: | Line 46: | ||
==Content sources== | ==Content sources== | ||
| − | + | Australian Standards Endpoint Location Service | |
| − | + | IHE HPD+ | |
| − | + | Argonaut Provider Directory Workgroup | |
| − | |||
==Example Scenarios== | ==Example Scenarios== | ||
| − | + | These resources are typically used to identify where to locate endpoint details for: | |
| − | + | •Questionnaires: Where to send information (currently an SDC extension with just the address) | |
| + | •ValueSet: Where related Terminology Services can be found (where not local) | ||
| + | •Subscription: The destination to send the subscribed data (or to pull) | ||
| + | •Messaging: (currently defined in the Message Header, but only as the address) | ||
| + | •Referrals: Where to send referral requests | ||
| + | (linked to the services directory resources - Organization/Location/Practitioner/HealthcareService) | ||
| + | •Referrals - Templates: Where to locate referral templates (Questionnaires) | ||
| + | (linked to the services directory resources - Organization/Location/Practitioner/HealthcareService) | ||
| + | •CarePlans: Where a shared CarePlan can be found | ||
| + | •Scheduling: Where to lookup to discover schedules/availability information | ||
| + | (linked to the services directory resources - Organization/Location/Practitioner/HealthcareService) | ||
| + | •Scheduling: Where to lookup to send appointment requests | ||
| + | (linked to the services directory resources - Organization/Location/Practitioner/HealthcareService) | ||
| + | •Patient/Person: Location of Master Patient/Person Indexes | ||
| + | •Service Provider Directories: Location of related directories (parent/child/federated) | ||
==Resource Relationships== | ==Resource Relationships== | ||
| + | The endpoint is distinct from a conformance statement in that the Conformance statement describes the entire capability of a server (and in the metadata case, just this server) | ||
| + | The endpoint resource describes the technical details for how to connect, and for what purposes (which could be a small sub-set of the server's capabilities, and may not be a FHIR endpoint). | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Timelines== | ==Timelines== | ||
| − | + | In time for the STU3 ballot cycle (draft is available now, and has been publicized and have a group willing to iterate on it quickly. | |
| − | |||
==gForge Users== | ==gForge Users== | ||
| − | + | brianpos | |
| − | |||
==When Resource Proposal Is Complete== | ==When Resource Proposal Is Complete== | ||
'''When you have completed your proposal, please send an email to [mailto:FMGcontact@HL7.org FMGcontact@HL7.org]''' | '''When you have completed your proposal, please send an email to [mailto:FMGcontact@HL7.org FMGcontact@HL7.org]''' | ||
Revision as of 20:46, 12 May 2016
This page documents a Pending FHIR Resource Proposal
Contents
- 1 Endpoint
- 1.1 Owning committee name
- 1.2 Committee Approval Date:
- 1.3 Contributing or Reviewing Work Groups
- 1.4 FHIR Resource Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 RIM scope
- 1.7 Resource appropriateness
- 1.8 Expected implementations
- 1.9 Content sources
- 1.10 Example Scenarios
- 1.11 Resource Relationships
- 1.12 Timelines
- 1.13 gForge Users
- 1.14 When Resource Proposal Is Complete
Endpoint
Owning committee name
Patient Administration
Committee Approval Date:
Please enter the date that the committee approved this Resource proposal
Contributing or Reviewing Work Groups
FHIR-Infrastructure
FHIR Resource Development Project Insight ID
pending
Scope of coverage
An endpoint describes the technical details of a location that can be connected to for the delivery/retrieval of information. Sufficient information is required to ensure that a connection can be made securely, and appropriate data transmitted as defined by the endpoint owner. This is not a description of details of the current system, as found in conformance, but of another (potentially external) system. These may be locally hosted services, regional services, or national service.
RIM scope
?
Resource appropriateness
All systems that integrate with other systems have a need to track the details of the connectivity. This resource permits recording of this information, and will be able to be included in Registries where they can be discovered, or internally to manage external dependencies.
Expected implementations
Content sources
Australian Standards Endpoint Location Service IHE HPD+ Argonaut Provider Directory Workgroup
Example Scenarios
These resources are typically used to identify where to locate endpoint details for: •Questionnaires: Where to send information (currently an SDC extension with just the address) •ValueSet: Where related Terminology Services can be found (where not local) •Subscription: The destination to send the subscribed data (or to pull) •Messaging: (currently defined in the Message Header, but only as the address) •Referrals: Where to send referral requests
(linked to the services directory resources - Organization/Location/Practitioner/HealthcareService)
•Referrals - Templates: Where to locate referral templates (Questionnaires)
(linked to the services directory resources - Organization/Location/Practitioner/HealthcareService)
•CarePlans: Where a shared CarePlan can be found •Scheduling: Where to lookup to discover schedules/availability information
(linked to the services directory resources - Organization/Location/Practitioner/HealthcareService)
•Scheduling: Where to lookup to send appointment requests
(linked to the services directory resources - Organization/Location/Practitioner/HealthcareService)
•Patient/Person: Location of Master Patient/Person Indexes •Service Provider Directories: Location of related directories (parent/child/federated)
Resource Relationships
The endpoint is distinct from a conformance statement in that the Conformance statement describes the entire capability of a server (and in the metadata case, just this server) The endpoint resource describes the technical details for how to connect, and for what purposes (which could be a small sub-set of the server's capabilities, and may not be a FHIR endpoint).
Timelines
In time for the STU3 ballot cycle (draft is available now, and has been publicized and have a group willing to iterate on it quickly.
gForge Users
brianpos
When Resource Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
