Skip to content
AENTE

§170.315(b)(10) Electronic Health Information export

AENTE Portal Overview

AENTE provides an easy tool for exporting all patient or facility history in JSON format. This structure facilitates interoperability across providers, enabling the exchange of patient data in a lightweight, easy-to-read format.

JSON Overview

This manual is designed to help users understand and interpret the JSON structure produced by the AENTE portal. The JSON file is divided into sections, each containing specific information about requests, customer data, appointments, and other relevant details. The resource-compressed report is responsible for exporting patient data in JSON format.

JSON Basics

  • Curly Braces {}: Define objects.
  • Square Brackets []: Define arrays.
  • Key-Value Pairs: Each key-value pair is separated by a colon :, with keys enclosed in double quotes.
  • Commas ,: Separate elements in an object or array.
  • Strings: Enclosed in double quotes ".
  • Numbers: Written as-is (e.g., 123, -45.67).
  • Booleans: Represented as true or false.
  • Null: Represented as null.

AENTE JSON Structure

The JSON object consists of two main sections:

  1. Header: Contains metadata about the request and location.
  2. Customer: Holds detailed information about the customer, including their context, appointments, and other data.

1.1 RequestInfo

Contains details about the user and request.

  • User:
    • ID: Unique identifier for the user who made the request.
    • Name: Full name of the user (e.g., Gabriel Rodrigues).
  • RequestTime: Timestamp when the request was made (e.g., 2024-12-06T20:32:13.147218Z).
  • ResourceType: Specifies the resource type (e.g., EMR).
  • Tag: documentation.aente.com
  • Token: Unique token for authentication of identification request (e.g., 66fa11dd-c7a0-49e4-991d-1c884552ce2a).
  • DateRange:
    • StartDate: The start of the date range (e.g., 2024-12-01).
    • EndDate: The end of the date range (e.g., 2024-12-31).

1.2 Location

Details about the request location.

  • LocationID: Unique identifier for the location (e.g., 112).
  • LocationName: Name of the location where the appointment or service ocurrerd. (e.g., AENTE INC.).
  • Taxonomy: Array of taxonomy classifications, if applicable (e.g., [207KA0200X]).
  • NPI: National Provider Identifier (e.g., null).
  • LocationPhone: Contact number (e.g., +1 714 334 2754).
  • LocationEmail: Contact email address (e.g., string).

Sample Section of Header in json

    "Header": {
            "RequestInfo": {
                "User": {
                    "ID": 2,
                    "Name": "Gabriel Rodrigues"
                },
                "RequestTime": "2024-12-06T20:32:13.147218Z",
                "ResourceType": "EMR",
                "Tag": null,
                "Token": "66fa11dd-c7a0-49e4-991d-1c884552ce2a",
                "DateRange": {
                    "StartDate": "2024-12-01",
                    "EndDate": "2024-12-31"
                }
            },
            "Location": {
                "LocationID": 112,
                "LocationName": "AENTE INC.",
                "Taxonomy": [],
                "NPI": "string",
                "LocationPhone": "+1 714 334 2754",
                "LocationEmail": null
            }
        },

2. Customer

The Customer section describes customer-related data, including main search criteria, patient context, encounter details, and appointment information.

2.1 CustomerID

Unique identifier for the customer (e.g., 2177).

2.2 MainSearchCriteria

Details of the main criteria used in the search.

  • code: ICD code set by provider (e.g., F43.1).
  • version: Version of the code system (e.g., 2024).
  • title: Descriptive title of the code (e.g., Post-traumatic stress disorder (PTSD)).
  • description: Join fo ICD’s Section, Block and Chapter (long text).

2.3 PatientContext

Demographic details and patient information.

Demographics

  • Name:
    • FirstName: First name (e.g., Logan).
    • MiddleName: Middle name (e.g., "").
    • LastName: Last name (e.g., Stark).
    • Suffix: Suffix, if applicable (e.g., string).
    • PreviousName: Previous names, if any (e.g., null).
    • NameToUse: Preferred name (e.g., null).
  • Contact:
    • Email: Email address (e.g., jenna2330@gmail.com).
    • Mobile: Mobile number (e.g., +1 775 962 1818).
  • Address:
    • Line1: Street address (e.g., string).
    • Line2: Additional address details (e.g., string).
    • City: City (e.g., Huntington Beach).
    • State: State (e.g., California).
    • Country: Country (e.g., United States).
    • PO.BOX: For Rural Areas (e.g., United States).
    • Postcode: Postal code (e.g., 92648).
  • ONC Standard:
    • Occupation: Occupation (e.g., null).
    • DateOfBirth: Birthdate (e.g., 1985-04-22).
    • Sex: Gender (e.g., null).
    • PreviousName: Previous Name if any.
    • NametoUse: User Choice variable.
    • Pronouns: User Choice variable.
    • Race: User Choice variable.
    • Ethnicity: User Choice variable.
    • TribalAffiliation: Affiliation with a tribe, if applicable.
    • SexualOrientation: Sexual orientation.
    • GenderIdentity: User Choice variable.
    • PreferredLanguage: User Choice variable.
    • PreviousAddress: Previous address
    • RelatedPersonName: User Choice variable.
    • RelationshipType: User Choice variable.
    • OccupationIndustry: User Choice variable.

Sample Section of Customer and Patient Context

    "Customer": {
            "CustomerID": 2177,
            "MainSearchCriteria": [
                {
                    "code": "F43.1",
                    "version": "2024",
                    "title": "Post-traumatic stress disorder (PTSD)",
                    "description": ""
                }
            ],
            "PatientContext": {
                "Demographics": {
                    "Suffix": "enum",
                    "LastName": "Stark",
                    "FirstName": "Logan",
                    "MiddleName": "",
                    "Email": "string",
                    "Mobile": "+1 000 000 0000",
                    "Address": {
                        "Line1": "String",
                        "Line2": "String",
                        "City": "Huntington Beach",
                        "State": "California",
                        "Country": "United States",
                        "Neighbourhood": "String",
                        "Number": "String",
                        "Postcode": "92648"
                    },
                    "Occupation": "String",
                    "DateOfBirth": "1985-04-22 00:00:00",
                    "Sex": "String",
                    "PreviousName": "String",
                    "NameToUse": "String",
                    "Pronouns": "String",
                    "DateOfDeath": "String",
                    "Race": "String",
                    "Ethnicity": "String",
                    "TribalAffiliation": "String",
                    "SexualOrientation": "String",
                    "GenderIdentity": "String",
                    "PreferredLanguage": "String",
                    "InterpreterNeeded": "String",
                    "PreviousAddress": "String",
                    "RelatedPersonName": "String",
                    "RelationshipType": "String",
                    "OccupationIndustry": "String"
                }

2.4 EncounterContext

Service Category name from online booking. All services have service categories

2.5 UserContext

Details of the user’s professional or provider context.

  • ProviderSpecialties: List of specialties, if any.

2.6 ProviderInfo

Information about the provider.

  • EmployeeID: Provider’s employee ID (e.g., 27).
  • EmployeeName: Provider’s name (e.g., Gabriel Rodrigues).

2.7 AppointmentInfo

Details of the appointment.

  • AppointmentID: Unique appointment identifier (e.g., 2933).
  • AppointmentName: Type of appointment (e.g., Primary Care - 75 Minutes (New Patient)).
  • Date: Appointment date (e.g., 2024-12-06T00:00:00.000000Z).
  • StartTime: Start time (e.g., 19:15:00).
  • EndTime: End time (e.g., 20:30:00).
  • PrimaryProcedure: CPT attached to the service booked in appointment (usually a 5 digit string).
  • ReferralList: List of referrals.
    • id: Unique ID for Referral ID (e.g., 190).
    • name: Referral name (e.g., Psychotherapy, 60 minutes with patient (CPT 90837)).
    • type: this is an enum for internal or external…
    • priority: this is an enum for severe or medium…
    • reason: text from provider for the referral reason
    • instructions: text from provider for the referral instructions

Sample Section of Customer and Patient Context

        "EncounterContext": [
            "wellbeing"
        ],
        "UserContext": {
            "ProviderSpecialties": []
        },
        "ProviderInfo": {
            "EmployeeID": 27,
            "EmployeeName": "Gabriel Rodrigues"
        },
        "AppointmentInfo": {
            "AppointmentID": 2933,
            "AppointmentName": "Primary Care - 75 Minutes (New Patient)",
            "Date": "2024-12-06T00:00:00.000000Z",
            "StartTime": "19:15:00",
            "EndTime": "20:30:00",
            "PrimaryProcedure": null,
            "ReferralList": [
                {
                    "id": 190,
                    "name": "Psychotherapy, 60 minutes with patient ( CPT 90837)"
                }
            ]
        },
    },

2.9 Form Settings and Form Items

A novel solution for managing data points and for observations. Both forms from Triage and EMR use the same module ‘form settings’

2.9.a Managing FORMS in 4 levels categories

All questions and/or observations that will require user input are managed in FORM-ITEMS. All questions must be included a FORM-CATEGORY. You may use the same FORM-ITEM in multiple FORM-CATEGORY. FORM-CATEGORY` have four levels for indexing and filtering.

2.9.b FORM-CATEGORY levels Explanation

  1. FirstDerived: The main category for indexing and filtering FirstDerivedClass
  2. SecondDerived: Child category to seperate form per service or procedure SecondDerivedClass.
  3. ThirdDerived: An array with priority for tab order viewing ThirdDerivedArray
  4. ForthDerived: Child Category that holds sections inside tabs of the interactive EMR. May be an array with priority for order viewing RelatedSectionsArray

2.10 TriageInfo & EMR FORMS

All services have the capability of attaching a form settings for user input. When a service has a selected form for triage this sections holds the data. All services have a primary CPT which may have a related FORM-CATEGORY.

Sample of Triage Objects

    "TriageInfo": {
        "BaseCategory": {
            "Name": "N\/A",
            "Description": "N\/A",
            "BaseCategoryID": "N\/A",
            "Type": "Category"
        },

Sample of EMR Objects

    "EMRForm": {
            "BaseCategory": {
                "Name": "N\/A",
                "Description": "N\/A",
                "BaseCategoryID": "N\/A",
                "Type": "Category"
            },

refer to section 2.9.b for FORM-CATEGORY and FORM-ITEM Module

  • BaseCategoy:

    • Description: Future Expansion for GIB-AI.
    • BaseCategoryID: Future Expansion for GIB-AI.
    • type: Future Expansion for GIB-AI.

  • FirstDerivedClass: -Name: Name of the categoy. -Description: Description of the categoy. -FirstDerivedClassID: Unique ID path meta for url -Type: form or section -SecondDerivedClass: CPT attached to the service booked in appointment (usually a 5 digit string). -Name: Name of the categoy. -Description: Description of the categoy. -SecondDerivedClassID: Unique ID path meta for url -Type: form or section -ThirdDerivedArray -Name: Name of the categoy. -Description: Description of the categoy. -TabID: Unique ID path meta for url -Type: form or section -Priority: show order of sections RelatedSectionsArray -Name: Name of the categoy. -Description: Description of the categoy. -SectionID: Unique ID path meta for url -Type: form or section -Priority: show order of sections ItemsDerivedArray -Name: Name of the categoy. -Description: Description of the categoy. -QuestionID: Unique ID path meta for url -Type: Unique ID path meta for url -Answer: Unique ID path meta for url

Sample Section FORM-SETTINGS

    "FirstDerivedClass": {
    "Name": "Evaluation and Management (E\/M) Services (99091-99499)",
    "Description": "E\/M codes are used for services that involve evaluating and managing a patient's health. They cover various types of visits and interactions between patients and healthcare providers.",
    "FirstDerivedClassID": "https:\/\/portal.aente.com\/public\/form_categories\/271",
    "Type": "Category",
    "SecondDerivedClass": {
        "Name": "(E.M.R) Psychotherapy, 60 minutes with patient (CPT 90837)",
        "Description": "E.M.R. Psychotherapy, 60 minutes with patient (CPT 90837)",
        "SecondDerivedClassID": "https:\/\/portal.aente.com\/public\/form_categories\/316",
        "Type": "Form",
        "ThirdDerivedArray": [
            {
                "Name": "S.O.A.P (90837)",
                "Description": "Structured clinical documentation based on the SOAP (Subjective, Objective, Assessment, Plan) format for psychotherapy services.",
                "TabID": "https:\/\/portal.aente.com\/public\/form_categories\/319",
                "Type": "Tab",
                "Priority": 1,
                "RelatedSectionsArray": [],
                "ItemsDerivedArray": [
                    {
                        "Name": "Subjective",
                        "Description": "Describe the patient's perspective, including their symptoms, concerns, and experiences as reported during the session.",
                        "QuestionID": "https:\/\/portal.aente.com\/public\/form_items\/670",
                        "Type": "Question",
                        "Answer": "<p>The patient, a 34-year-old, reports experiencing occasional flashbacks and nightmares following a car accident three months ago. They describe feeling \"on edge\" in crowded places and avoiding driving on highways. The patient denies significant sleep disturbances but mentions occasional restlessness. They report mild irritability and difficulty concentrating at work but state it has not severely impacted daily functioning. They express concern about their ability to manage these feelings and seek help proactively.<\/p>"
                    },
                    {
                        "Name": "Objective",
                        "Description": "Document observations and measurable findings during the session, including appearance, behavior, and cognitive functioning.",
                        "QuestionID": "https:\/\/portal.aente.com\/public\/form_items\/671",
                        "Type": "Question",
                        "Answer": "<p>The patient appears well-groomed and calm during the visit. Speech is coherent, with no signs of agitation or distress observed. Affect is appropriate but mildly restricted. The patient maintains eye contact and answers questions thoughtfully. No evidence of cognitive impairments or thought abnormalities was noted during the mental status examination.<\/p>"
                    },
                    {
                        "Name": "Assessment",
                        "Description": "Provide a clinical evaluation or diagnosis based on the information gathered during the session.",
                        "QuestionID": "https:\/\/portal.aente.com\/public\/form_items\/672",
                        "Type": "Question",
                        "Answer": "<p>The patient exhibits mild symptoms consistent with post-traumatic stress disorder (PTSD), including avoidance, hypervigilance, and occasional flashbacks, without significant functional impairment.<\/p>"
                    },
                    {
                        "Name": "Plan",
                        "Description": "Outline the proposed course of action, including treatment plans, referrals, and follow-up arrangements.",
                        "QuestionID": "https:\/\/portal.aente.com\/public\/form_items\/673",
                        "Type": "Question",
                        "Answer": "<ol><li>Provide psychoeducation on PTSD and its symptoms.<\/li><li>Recommend starting trauma-focused cognitive-behavioral therapy (CBT).<\/li><li>Suggest mindfulness exercises and deep-breathing techniques to reduce hyperarousal.<\/li><li>Schedule follow-up in four weeks to monitor progress and reassess treatment needs.<\/li><\/ol><p><br><\/p>"
                    }
                ]
            }
        ]
    }
}

Conclusion

AENTE offers a robust module designed to generate compressed job reports in JSON format, facilitating seamless interoperability with external systems. Users have the flexibility to view their records in PDF format within each appointment or export the data as JSON files for further use.

It is important to note that once reports are exported from the AENTE database, they are no longer protected by AENTE’s security protocols. Users are encouraged to implement appropriate safeguards to ensure the privacy and security of the exported data.