fhir-documentation.patientmedrecords.com Open in urlscan Pro
2600:9000:2644:8c00:8:5a85:d340:93a1  Public Scan

Form analysis
0 forms found in the DOM

Text Content

You need to enable JavaScript to run this app.
HomeResourcesClient RegistrationAPI Error MessagesFHIR Endpoints

OFFICE PRACTICUM FHIR DOCUMENTATION

Office Practicum (OP) is an EHR system that captures various clinical,
demographic, and practice related information. OP’s goal is to integrate with
external vendors and systems as easily and securely as possible to help
encourage interoperability opportunities for its practices. For external vendors
looking to integrate with OP, we recommend developing to the Fast Healthcare
Interoperability Resources (FHIR) standard. OP offers a full specification of
API requirements that are capable of supporting various integrated workflows.
Vendors can develop FHIR APIs according to OP specifications*, connect their
systems and applications of choice to the OP platform, and facilitate their own
integrated solution.

SUMMARY OF RESOURCES

VERSION R4



SUPPORTED SCOPES

 * launch/patient
 * openid
 * fhirUser
 * offline_access
 * user/Medication.read
 * user/AllergyIntolerance.read
 * user/CarePlan.read
 * user/CareTeam.read
 * user/Condition.read
 * user/Device.read
 * user/DiagnosticReport.read
 * user/DocumentReference.read
 * user/Encounter.read
 * user/Goal.read
 * user/Immunization.read
 * user/Location.read
 * user/MedicationRequest.read
 * user/Observation.read
 * user/Organization.read
 * user/Patient.read
 * user/Practitioner.read
 * user/Procedure.read
 * user/Provenance.read
 * user/PractitionerRole.read
 * system/Medication.read
 * system/AllergyIntolerance.read
 * system/CarePlan.read
 * system/CareTeam.read
 * system/Condition.read
 * system/Device.read
 * system/DiagnosticReport.read
 * system/DocumentReference.read
 * system/Encounter.read
 * system/Goal.read
 * system/Immunization.read
 * system/Location.read
 * system/MedicationRequest.read
 * system/Observation.read
 * system/Organization.read
 * system/Patient.read
 * system/Practitioner.read
 * system/Procedure.read
 * system/Provenance.read
 * system/PractitionerRole.read
 * patient/Medication.read
 * patient/AllergyIntolerance.read
 * patient/CarePlan.read
 * patient/CareTeam.read
 * patient/Condition.read
 * patient/Device.read
 * patient/DiagnosticReport.read
 * patient/DocumentReference.read
 * patient/Encounter.read
 * patient/Goal.read
 * patient/Immunization.read
 * patient/Location.read
 * patient/MedicationRequest.read
 * patient/Observation.read
 * patient/Organization.read
 * patient/Patient.read
 * patient/Practitioner.read
 * patient/Procedure.read
 * patient/Provenance.read
 * patient/PractitionerRole.read

SOFTWARE COMPONENTS AND CONFIGURATIONS

1. SAFETY GUIDELINES

The apps should reasonably adhere to usability standards that impact patient
information safety. If the app allows an end user to search for a patient, the
app should collect enough information from the end user to uniquely identify the
correct patient or display enough information to the end user to enable the end
user to uniquely identify the correct patient.

2: SECURITY GUIDELINES

Office Practicum supports securing, sending, or receiving data securely with the
TLS 1.2 or higher encryption protocol. The apps can verify that the server's TLS
certificate is valid and signed by a certificate authorized, recognized, and
trusted by the host operating system.

Data exchange between the apps and Office Practicum’s API's should be secured
with industry standard encryption while in transit, and use authentication and
authorization protocols. The preferred mechanism for the apps to authorize with
Office Practicum is SMART on FHIR OAuth 2.0 protocol. The apps should be able to
protect authorization credentials provided by Office Practicum, such as user
names, user passwords, access tokens, or refresh tokens.

The app client identifiers should be kept confidential and should not disclose
them to any other party or use them for any other purpose. Each app will have
its own unique client identifier. Apps that are confidential clients and using
refresh tokens should keep their client secret safe.

3: SUPPORTED FORMATS

The apps should reasonably adhere to usability standards that impact patient
information safety. If the app allows an end user to search for a patient, the
app should collect enough information from the end user to uniquely identify the
correct patient or display enough information to the end user to enable the end
user to uniquely identify the correct patient.

4. METHOD FOR ISSUANCE OF INITIAL REFRESH TOKEN

This is the method by which Office Practicum supports the secure issuance of an
initial refresh token to native applications:
https://datatracker.ietf.org/doc/html/draft-ietf-oauth-dyn-reg

ABOUT US

Connexin Software, Inc.

602 W Office Center Dr Suite 350

Fort Washington, PA 19034

QUICK LINKS

Contact

Terms of Use

Privacy Policy

Frequently Asked Questions (FAQs)

Legacy Atlas Identifiers

Revoke App Access

Office Practicum FHIR Documentation ® 2024

Home
Resources
Client Registration
API Error Messages
FHIR Endpoints