- Organization hierarchy is allowed but not required
- Location must have 1..1 Organization
- PractitionerRole must have 1..1 Organization
- PractitionerRole must have 1..1 Practitioner
- PractitionerRole must have 1..1 Location
- HealthcareService must have 1..1 Organization
- HealthcareService must have 1..1 Location
- Organization has 0..0 Endpoint
- HealthcareService may have 0..* Endpoint
- Location must have 0..0 Endpoint
- ProviderRole may have 0..* Endpoint
- Practitioner must have 0..0 address
- Endpoint Extension: Receiving Application
- Endpoint Extension: Receiving Facility (HD)
- Endpoint need Extension for certificate (needs discussion)
- Endpoint.connectionType - SMD will use already defined http://ns.electronichealth.net.au/browse-service-interface.html; require one code of this system
- http://ns.electronichealth.net.au/smd/intf/SealedImmediateMessageDelivery/TLS/2010
- http://ns.electronichealth.net.au/smd/intf/SealedMessageDelivery/TLS/2010
- http://ns.electronichealth.net.au/smd/intf/SealedMessageRetrieval/TLS/2010
- http://ns.electronichealth.net.au/smd/intf/TransportResponseDelivery/TLS/2010
- http://ns.electronichealth.net.au/smd/intf/TransportResponseRetrieval/TLS/2010
Do this as Coding e.g.
{ system="http://ns.electronichealth.net.au/smd/intf", code="http://ns.electronichealth.net.au/smd/intf/SealedMessageDelivery/TLS/2010"}
- Endpoint.payloadType - use already defined http://ns.electronichealth.net.au/browse-service-category.html; require one code of this system
{ system="http://ns.electronichealth.net.au/smd/sc", code="??"} - Endpoint.payloadMimeType - no constraints for SM
- Note: concerns on HealthcareService must have 1..1 Location (too constrained?)
- Note: could publish endpoints on HealthcareService and/or Location as desired by advertiser
- Layer a exclusion layer IG (explicit PD) on top of compliant PD requirements IG
- Need a working party on specialty/role code for PractitionerRole; service type coding HealthcareService



