Response: Array of claims objects
[
{
id: 7498923432,
date: 'June 10, 2016', (or whatever format)
amount: 430.00, (or whatever format)
memberName: 'John Smith', (cna be fname and lname too, whatever is easier)
healthplan: 'BCBS FL',
status: true, (this is just for "Paid' or "Not Paid"... not sure if there is other status's, if there is just send back the status string I guess)
provider: 'Dr. Davis',
}
]
I do not need this endpoint if you can give me all the info in GET /claims, it is not alot so we can maybe get away with just the list
ResponseE: Array of objects of Power of Attorney contacts
[
{
fName: 'John',
lName: 'Morgan',
relationship: 'Attorney',
phone: '3335679894',
address: '20 N Orange Ave Suite 1600 Orlando FL 32801',
email: 'john@morgan.com'
}
]
Response: Array of objects of provider contacts
[
{
address: '4539 S Dale Mabry Hwy #110, Tampa, FL 33611',
phone: '5557672334',
fName: 'Dr. Christopher',
lName: 'Davis',
title: 'Advanced Rehabilitation'
}
]
Response
{
plan: 'Blue Cross PPO',
type: 'Medi-Cal',
effectiveDate: '1/1/2017', (whatever format)
termDate: '12/31/2017', (whatever format)
}
Response
{
fName: 'Robert',
lName: 'Johnson',
address: '3006 W Azeele St, Tampa, FL 33609',
phone: '5551230987'
}
Response: Array of objects of specialties
[
{
name: 'Acupuncture',
id: 1
},
{
name: 'Orthopedic',
id: 2
}
]
Not 100% how the search should work
Request: something like (only going to require that at least 1 field is set):
{
fName: 'Bob',
lName: 'Smith',
practiceName: 'Docs R Us',
state: 'FL',
zip: '33123',
specialty: '5' (I will be sending back to you the 'id' number from the specialties from /directory/specialties)
}
Response: array of objects
[
{
title: 'Orthopaedic Medical Group of Tampa Bay',
address: '4541 S Dale Mabry Hwy, Tampa, FL 33611',
phone: 18135559986,
other: ['Orthopedic, Surgery'] <-- array of the practice's specialties
}
]
Response
{
max: 5000,
current: 1200,
totalClaims: 12 <-- not sure if this belongs or not, this is just the total claims, I imagine you can get this when you are totalling the current amount the user has spent towards the deductible
}
Response
{
name: 'John Smith', <-- can be fName, lName, etc, this is just whoevers name is on the card I guess?
cardID: 'ZXY42343423423234',
groupID: '99',
coverageDate: '1/1/2017' (whatever format)
}
This is pretty basic, maybe we should send in more info about the user? Like addresses and stuff?
Response
{
fName: 'Bob;,
lName: 'Smith',
memberId: '213ZXYABC1234'
}
Request:
{
memberId: '123456789',
fName: 'Bob',
lName: 'Smith',
userId: '123' <-- I have no idea what this is, it was in the old app
email: 'bob@bob.com',
password: 'password'
}
Response
{
result: 'success'
}
Request:
{
current: 'currentPassword',
new: 'newPassword'
}
Response
{
result: 'success'
}
Request:
{
email: 'bob@bob.com'
}
Response
{
result: 'success'
}
In the password email, please send them to /guest/forgotpass?token=whatever
This is for the password reset via email, you will send them a link to /guest/forgotpass?token=whatever
Request:
{
new: 'password',
token: 'sometoken'
}
Response
{
result: 'success'
}
Request:
{
user: 'user@email.com',
pass: 'password',
client_id: 'clientSecret',
grant_type: 'token'
}
Response
{
token: 'somelongtoken',
refreshToken: 'someotherlongtoken',
}
For refreshing tokens
Request:
{
client_id: 'clientSecret',
grant_type: 'refresh',
refreshToken: 'somelongtoken'
}
Response
{
token: 'somelongtoken',
refreshToken: 'someotherlongtoken',
}
I will send you the current tokens so you can invalidate them
Request:
{
token: 'somelongtoken',
refreshToken: 'someotherlongtoken',
client_id: 'clientSecret'
}
Response
{
result: 'success'
}