Create Person
Use the PatientCareIntegrationV2_createPerson method to create a legal entity in Patient Care.
This method lets you register the company's main registration data, such as legal name, trade name, phone number, document, country, and person type.
Step 1: Get the Authentication Token and Headers
Before performing any operation, you must authenticate and obtain a valid token.
This endpoint uses the Patient Care authentication flow.
For more details, see: Patient Care Authentication
Step 2: Create Person
Use the PatientCareIntegrationV2_createPerson method to create a company in Patient Care.
Parameters
| Parameter | Type | Required | Description | Value |
|---|---|---|---|---|
| input | Object | Yes | Legal entity registration data | Object |
Input Fields
| Field | Type | Required | Description |
|---|---|---|---|
| programSlug | String | Yes | Program identifier in Patient Care. Possible values - programSlug |
| name | String | Yes | Company legal name |
| socialName | String | No | Company trade name |
| mainPhone | String | No | Main phone number |
| typeMainPhone | Enum | No | Main phone type. Possible values - typeMainPhone |
| document | String | Yes | Company document, CNPJ, numbers only |
| country | Enum | Yes | Country. Possible values - country |
| typePerson | Enum | Yes | Person type. Possible values - typePerson |
| subTypePerson | Int | No | Person subtype. Possible values - subTypePerson |
| String | No | Company email | |
| observation | String | No | Additional registration notes |
Possible values - programSlug
| Value | Description |
|---|---|
| teva_sac | Teva SAC Program |
| teva_cuidar | Teva Cuidar Program |
Possible values - typeMainPhone
| Value | Description |
|---|---|
| _0 | Residential |
| _1 | Commercial |
| _2 | Mobile |
| _3 | Message |
Possible values - country
| Value | Country |
|---|---|
| _0 | Brazil |
| _1 | Peru |
| _2 | Mexico |
Possible values - typePerson
| Value | Description |
|---|---|
| _0 | Individual |
| _1 | Legal Entity |
Possible values - subTypePerson
| Value | Description |
|---|---|
| 0 | Caregiver |
| 1 | Distributor |
| 2 | Student |
| 3 | Pharmacy |
| 4 | Laboratory |
| 5 | Representative |
| 6 | Other Healthcare Professionals |
| 7 | Anonymous |
| 8 | Consumer |
GraphQL Mutation Example
mutation createPerson {
PatientCareIntegrationV2_createPerson(
input: {
programSlug: "teva_cuidar"
name: "EMPRESA EXEMPLO LTDA"
socialName: "EMPRESA EXEMPLO"
mainPhone: "11999999999"
typeMainPhone: _1
document: "12345678000199"
country: _0
typePerson: _1
subTypePerson: 0
email: "empresa.exemplo@email.com"
observation: "Cadastro de teste"
}
) {
idPerson
name
socialName
mainPhone
typeMainPhone
document
country
typePerson
subTypePerson
email
observation
}
}
Return Example
{
"data": {
"PatientCareIntegrationV2_createPerson": {
"idPerson": "d96ef1b7-8fe0-4a62-ae07-6d7efde03d10",
"name": "EMPRESA EXEMPLO LTDA",
"socialName": "EMPRESA EXEMPLO",
"mainPhone": "11999999999",
"typeMainPhone": "_1",
"phone2": null,
"typePhone2": null,
"phone3": null,
"typePhone3": null,
"document": "12345678000199",
"country": "_0",
"typePerson": "_1"
}
}
}
Notes
- The
programSlugfield identifies the program in Patient Care. - The
documentfield must be sent with numbers only. - The
typeMainPhone,country, andtypePersonfields use enumerated values. - The
subTypePersonfield uses numeric values according to the types available in the integration. - Optional fields may be omitted when no information is available.