This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Endpoint FHIR Resource Proposal"
Jump to navigation
Jump to search
| (11 intermediate revisions by one other user not shown) | |||
| Line 3: | Line 3: | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
| − | This page documents a [[:category: | + | This page documents a [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] |
</div> | </div> | ||
</div> | </div> | ||
[[Category:FHIR Resource Proposal]] | [[Category:FHIR Resource Proposal]] | ||
| − | [[Category: | + | [[Category:Approved FHIR Resource Proposal]] |
| Line 19: | Line 19: | ||
==Committee Approval Date:== | ==Committee Approval Date:== | ||
| − | + | 31 May 2016 | |
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
| Line 28: | Line 28: | ||
==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 | + | 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 in an agreed format (such as IHE or HL7 Profiles). |
| − | |||
| − | |||
| + | 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== | ||
| Line 43: | Line 43: | ||
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
| − | *Public Services/Provider Directories | + | *Public Services/Provider Directories which assist in electronic data transfers |
*Systems that maintain connections to external systems | *Systems that maintain connections to external systems | ||
| Line 50: | Line 50: | ||
*IHE HPD+ | *IHE HPD+ | ||
*Argonaut Provider Directory Workgroup | *Argonaut Provider Directory Workgroup | ||
| + | *Carequality UDDI | ||
==Example Scenarios== | ==Example Scenarios== | ||
| Line 56: | Line 57: | ||
*ValueSet: Where related Terminology Services can be found (where not local) | *ValueSet: Where related Terminology Services can be found (where not local) | ||
*Subscription: The destination to send the subscribed data (or to pull) | *Subscription: The destination to send the subscribed data (or to pull) | ||
| − | *Messaging: (currently defined in the Message Header, but only as the address) | + | *Messaging: (currently defined in the Message Header, but only as the address) eg CCDA distribution |
| − | *Referrals: Where to send referral requests | + | *Referrals: Where to send referral requests (linked to the services directory resources - Organization/Location/Practitioner/HealthcareService) |
| − | (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) |
| − | *Referrals - Templates: Where to locate referral templates (Questionnaires | ||
| − | |||
*CarePlans: Where a shared CarePlan can be found | *CarePlans: Where a shared CarePlan can be found | ||
| − | *Scheduling: Where to lookup to discover schedules/availability information | + | *Scheduling: Where to lookup to discover schedules/availability information (linked to the services directory resources - Organization/Location/Practitioner/HealthcareService) |
| − | (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) |
| − | *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 | *Patient/Person: Location of Master Patient/Person Indexes | ||
*Service Provider Directories: Location of related directories (parent/child/federated) | *Service Provider Directories: Location of related directories (parent/child/federated) | ||
| + | *Imaging: Locating DICOM servers that will contain the HIRES images | ||
==Resource Relationships== | ==Resource Relationships== | ||
| Line 73: | Line 71: | ||
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). | 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). | ||
| + | |||
| + | The endpoint may be referenced by | ||
| + | *Organization | ||
| + | *Location | ||
| + | *HealthcareService | ||
==Timelines== | ==Timelines== | ||
Latest revision as of 20:23, 20 July 2016
This page documents a Approved 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:
31 May 2016
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 in an agreed format (such as IHE or HL7 Profiles).
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
(none)
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
- Public Services/Provider Directories which assist in electronic data transfers
- Systems that maintain connections to external systems
Content sources
- Australian Standards Endpoint Location Service
- IHE HPD+
- Argonaut Provider Directory Workgroup
- Carequality UDDI
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) eg CCDA distribution
- 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)
- Imaging: Locating DICOM servers that will contain the HIRES images
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).
The endpoint may be referenced by
- Organization
- Location
- HealthcareService
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
