Yes. The implementation is documented in the Capability Statement available at the /metadata endpoint.
No. Per the FHIR specification, the /metadata endpoint does NOT require authorization.
Yes, all transactions with the service MUST use TLS.
Yes, the Task resource is profiled to constrain the intent property and to require a contained Patient resource holding the demographic data for patient matching.
The input and output property types of the Task resource are described using value sets defined for this implementation.
This depends on the capabilities of the data providers, but the documents will typically be Consolidated CDA documents in XML format.
Updated 11 months ago