post https://fhir-api.zapehr.com/r4b/OrganizationAffiliation
OrganizationAffiliation on the FHIR specification website.
Defines an affiliation/assotiation/relationship between 2 distinct oganizations, that is not a part-of relationship/sub-division relationship.
The body should be a valid FHIR object for OrganizationAffiliation.
Here is an example:
{
"resourceType": "OrganizationAffiliation",
"id": "example",
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t<p>\n\t\t\t\tHL7 Payer Network services for Acme Hospital from 1-Jan 2012 to 31-Mar 2012\n\t\t\t</p>\n\t\t</div>"
},
"identifier": [
{
"system": "http://www.acme.org/practitioners",
"value": "23"
}
],
"active": true,
"period": {
"start": "2012-01-01",
"end": "2012-03-31"
},
"organization": {
"reference": "Organization/hl7pay"
},
"participatingOrganization": {
"reference": "Organization/f001"
},
"network": [
{
"reference": "Organization/hl7pay",
"display": "HL7 Payer Network"
}
],
"code": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/organization-role",
"code": "provider"
}
]
}
],
"specialty": [
{
"coding": [
{
"system": "http://snomed.info/sct",
"code": "408443003",
"display": "General medical practice"
}
]
}
],
"location": [
{
"reference": "Location/1",
"display": "South Wing, second floor"
}
],
"healthcareService": [
{
"reference": "HealthcareService/example"
}
],
"telecom": [
{
"system": "email",
"value": "[email protected]",
"use": "work"
}
],
"endpoint": [
{
"reference": "Endpoint/example"
}
]
}
You can reference the FHIR documentation to determine the format for OrganizationAffiliation.